Scheduling systems and methods for wireless networks

ABSTRACT

In one embodiment, a method is performed by a base station in a wireless network. The method includes receiving from a user device a request to reconfigure already-active uplink semi-persistent scheduling (SPS). The already-active uplink SPS grants the user device a resource block allocation (RBA) and a modulation and coding scheme (MCS) for periodic uplink transmissions. The already-active uplink SPS includes a time-interval parameter, the time-interval parameter specifying a time interval between the periodic uplink transmissions. The request includes information related to a proposed adjustment of the time-interval parameter. The method further includes reconfiguring the already-active uplink SPS. The reconfiguring includes modifying the time-interval parameter based, at least in part, on the information.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is a continuation of U.S. application Ser. No.15/996,094, filed on Jun. 1, 2018, which is a continuation of U.S.application Ser. No. 14/666,799, filed on Mar. 24, 2015, now issued asU.S. Pat. No. 10,004,060 on Jun. 19, 2018, which claims priority from,and incorporates by reference the entire disclosure of, U.S. ProvisionalPatent Application No. 61/970,105, filed Mar. 25, 2014. This patentapplication claims priority from, and incorporates by reference theentire disclosure of, U.K. Patent Application No. 1408865.2, filed May19, 2014 and U.K. Patent Application No. 1408817.3, filed May 19, 2014.

BACKGROUND Technical Field

The present disclosure relates generally to wireless networks and moreparticularly, but not by way of limitation, to scheduling systems andmethods for wireless networks.

History of Related Art

In Long Term Evolution (LTE) networks, scheduling decisions are normallydynamic. That is, every transmission time interval (TTI) (e.g., 1millisecond), a base station can decide which wireless devices will beallocated resources for transmission in the uplink and downlink, alongwith the transmission parameters such as modulation, coding, antennas,etc. Since the scheduling decision can change every TTI, it has to besignaled to the wireless devices every TTI. While dynamic scheduling canbe well suited for bursty data applications, it has some disadvantagesfor voice. Voice is natively carried in LTE networks as Voice overInternet Protocol (VoIP) packets, which have a small payload (e.g.,20-50 bytes). Due to the small payload, the relative overhead resultingfrom the dynamic scheduling signaling can be very high.

SUMMARY OF THE INVENTION

In one embodiment, a method is performed by a base station in a wirelessnetwork. The method includes receiving from a user device a request toreconfigure already-active uplink semi-persistent scheduling (SPS). Thealready-active uplink SPS grants the user device a resource blockallocation (RBA) and a modulation and coding scheme (MCS) for periodicuplink transmissions. The already-active uplink SPS includes atime-interval parameter, the time-interval parameter specifying a timeinterval between the periodic uplink transmissions. The request includesinformation related to a proposed adjustment of the time-intervalparameter. The method further includes reconfiguring the already-activeuplink SPS. The reconfiguring includes modifying the time-intervalparameter based, at least in part, on the information.

In one embodiment, a method is performed by a user device in a wirelessnetwork. The method includes identifying a proposed adjustment to atime-interval parameter of already-active uplink semi-persistentscheduling (SPS). The already-active uplink SPS grants the user device aresource block allocation (RBA) and a modulation and coding scheme (MCS)for periodic uplink transmissions. The already-active uplink SPScomprises a time-interval parameter, the time-interval parameterspecifying a time interval between the periodic uplink transmissions. Inaddition, the method includes transmitting to a base station a requestto reconfigure the already-active uplink SPS, the request comprisinginformation related to the proposed adjustment.

In one embodiment, a method is performed by a base station in a wirelessnetwork. The method includes receiving from a user device a request toreconfigure already-active uplink semi-persistent scheduling (SPS) toaccommodate at least one packet-size change. The already-active uplinkSPS includes a modulation and coding scheme (MCS) and a resource blockallocation (RBA) for periodic uplink transmissions. The request includesinformation related to a size of each of one or more future uplinkpackets. The method further includes reconfiguring the already-activeuplink SPS. The reconfiguring includes modifying at least one of the RBAand the MCS to accommodate at least a next packet of the one or morefuture uplink packets.

In one embodiment, a method is performed by a user device in a wirelessnetwork. The method includes determining at least one packet-size changein one or more future uplink packets. The method further includestransmitting to a base station a request to reconfigure already-activeuplink SPS to accommodate the at least one packet-size change. Thealready-active uplink SPS includes a modulation and coding scheme (MCS)and a resource block allocation (RBA) for periodic uplink transmissions.The request includes information related to a size of the one or morefuture uplink packets.

In one embodiment, a method is performed by a base station in a wirelessnetwork. The method includes detecting a trigger, by a user devicesubject to already-active uplink semi-persistent scheduling (SPS), of aSPS-reconfiguration event. The already-active uplink SPS grants the userdevice a resource block allocation (RBA) and a modulation and codingscheme (MCS) for periodic uplink transmissions. The already-activeuplink SPS comprises a time-interval parameter, the time-intervalparameter specifying a time interval between the periodic uplinktransmissions. The detected trigger comprises transmission by the userdevice of one or more empty packets. The SPS-reconfiguration event isassociated with a preconfigured adjustment to at least one configurationparameter of the already-active uplink SPS. The method further includesreconfiguring the already-active uplink SPS based, at least in part, onthe preconfigured adjustment.

In one embodiment, a method is performed by a user device in a wirelessnetwork. The method includes identifying at least one configurationparameter of already-active uplink semi-persistent scheduling (SPS) foradjustment. The already-active uplink SPS grants the user device aresource block allocation (RBA) and a modulation and coding scheme (MCS)for periodic uplink transmissions. The already-active uplink SPScomprises a time-interval parameter, the time-interval parameterspecifying a time interval between the periodic uplink transmissions.The method further includes, responsive to the identifying, triggering aSPS-reconfiguration event. The triggering includes transmitting to abase station one or more empty packets. The SPS-reconfiguration event isassociated with a preconfigured adjustment to the at least oneconfiguration parameter.

In one embodiment, a method is performed by a base station in a wirelessnetwork. The method includes, responsive to a reconfigurationdetermination, reconfiguring already-active downlink semi-persistentscheduling (SPS) to accommodate a plurality of non-uniformly-sizedfuture downlink packets. The already-active downlink SPS grants a userdevice a resource block allocation (RBA) and a modulation and codingscheme (MCS) for periodic downlink transmissions. The already-activedownlink SPS includes a time-interval parameter, the time-intervalparameter specifying a time interval between the periodic downlinktransmissions. The method further includes sending to the user device anotification of the reconfigured already-active downlink SPS, thenotification including information related to a size of each of theplurality of non-uniformly-sized future downlink packets.

In one embodiment, a method is performed by a user device in a wirelessnetwork. The method includes receiving from a base station anotification of reconfigured downlink semi-persistent scheduling (SPS).The reconfigured downlink SPS reconfigures already-active downlink SPSto accommodate a plurality of non-uniformly-sized future downlinkpackets. The already-active downlink SPS grants the user device aresource block allocation (RBA) and a modulation and coding scheme (MCS)for periodic downlink transmissions. The already-active downlink SPScomprises a time-interval parameter, the time-interval parameterspecifying a time interval between the periodic downlink transmissions.The notification includes information related to a size of each of theplurality of non-uniformly-sized future downlink packets. In addition,the method includes implementing the reconfigured downlink SPS.

In one embodiment, a method is performed by a base station in a wirelessnetwork. The method includes, responsive to a reconfigurationdetermination, reconfiguring already-active downlink semi-persistentscheduling (SPS). The reconfiguring includes modifying a time-intervalparameter of the already-active downlink SPS. The already-activedownlink SPS grants a user device a resource block allocation and amodulation and coding scheme (MCS) for periodic downlink transmissions.The time-interval parameter specifies a time interval between theperiodic downlink transmissions. The method further includes sending tothe user device a notification of the reconfigured already-activedownlink SPS. In addition, the method includes determining one or moretimes when the user device should send a channel status report (CSR) tothe base station based, at least in part, on the modified time-intervalparameter. The method also includes transmitting to the user deviceinformation sufficient to identify the determined one or more times.

In one embodiment, a method is performed by a user device in a wirelessnetwork. The method includes receiving, from a base station, anotification of reconfigured downlink SPS. The reconfigured downlink SPSreconfigures already-active downlink SPS. The already-active downlinkSPS grants the user device a resource block allocation (RBA) and amodulation and coding scheme (MCS) for periodic downlink transmissions.The already-active downlink SPS includes a time-interval parameter, thetime-interval parameter specifying a time interval between the periodicdownlink transmissions. The reconfigured downlink SPS includes amodified time-interval parameter. The method further includes receivingfrom the base station information sufficient to identify one or moretimes at which a channel status report (CSR) should be sent.

The above summary is not intended to represent each embodiment or everyaspect of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the method and apparatus of the presentdisclosure may be obtained by reference to the following DetailedDescription when taken in conjunction with the accompanying Drawingswherein:

FIG. 1 illustrates an example of a wireless communication system thatcan facilitate SPS reconfiguration.

FIG. 2A illustrates an example VoIP coding and communicating process fora transmitter and receiver.

FIG. 2B illustrates examples of R-mode and O-mode operations.

FIG. 3 illustrates user equipment that can facilitate SPSreconfiguration.

FIG. 4 is a illustrates an LTE network architecture.

FIG. 5 illustrates an example of a radio protocol architecture for theuser and control planes in LTE.

FIG. 6 illustrates an eNB in communication with a user equipment (UE).

FIG. 7 illustrates an example of a process for performing uplink SPSreconfiguration.

FIG. 8 illustrates an example of a signaling timeline for uplink SPSreconfiguration.

FIG. 9 illustrates an example of a signaling timeline for uplink SPSreconfiguration.

FIG. 10 illustrates an example of a signaling timeline for uplink SPSreconfiguration.

FIG. 11 illustrates an example of a signaling timeline for uplink SPSreconfiguration.

FIG. 12 illustrates an example of a signaling timeline for uplink SPSreconfiguration.

FIG. 13 illustrates an example of a signaling timeline for uplink SPSreconfiguration.

FIG. 14 illustrates an example of using a reserved bit to identifyreconfiguration settings.

FIG. 15A illustrates an example of a SPS reconfiguration for an initialtalk spurt and a subsequent talk spurt.

FIG. 15B illustrates an example of SPS reconfiguration for a silenceinterval.

FIG. 15C illustrates an example of SPS reconfiguration for a silenceinterval.

FIG. 16 illustrates an example of a process for UE establishment of SPSreconfiguration settings.

FIG. 17 illustrates an example of a signaling timeline for accomplishingtransfer of uplink SPS reconfiguration settings from a UE to an eNB.

FIG. 18 illustrates an example of a signaling timeline for accomplishingtransfer of uplink SPS reconfiguration settings from a UE to an eNBusing RRC signaling.

FIG. 19 illustrates an example of a process for eNB establishment ofuplink SPS reconfiguration settings.

FIG. 20 illustrates an example of a signaling timeline for accomplishingtransfer of uplink SPS reconfiguration settings from an eNB to a UE.

FIG. 21 illustrates an example of a process for performing implicituplink SPS reconfiguration.

FIG. 22 illustrates an example of a timeline for implicitreconfiguration of uplink SPS.

FIG. 23 illustrates an example of a process for performing downlink SPSreconfiguration.

FIG. 24 illustrates an example of a process for performing CSRoptimization.

FIG. 25 illustrates an example of a timeline for reporting.

FIG. 26 illustrates an example of a process for performing implicitdownlink SPS reconfiguration.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

In wireless telecommunications systems, a base station can exchangesignals with user equipment (UE) located in a geographical region knownas a cell. A particular base station may also be referred to by thoseskilled in the art as an evolved Node B (eNB), a base transceiverstation, a radio base station, a radio transceiver, a transceiverfunction, or as some other suitable term. For illustrative purposes, theterm “eNB” may be periodically used herein in order to provide examplesrelative to Long Term Evolution (LTE) networks. However, it should beappreciated that each such utilization should be considered to furtherencompass meanings associated with any suitable term for a base station,including the illustrative terms listed above.

Examples of UEs include a cellular phone, a smart phone, a wearable orbody-borne computer, a session initiation protocol (SIP) phone, adesktop computer, a laptop computer, a tablet computer, a personaldigital assistant (PDA), a global positioning system, a multimediadevice, a video device, a digital audio player (e.g., MP3 player), acamera, a game console, a set-top box, or any other similar functioningdevice. A particular UE may also be referred to by those skilled in theart as a mobile station, a subscriber station, a mobile unit, asubscriber unit, a wireless unit, a remote unit, a mobile device, awireless device, a wireless communications device, a user device, anend-user device, a remote device, a mobile subscriber station, an accessterminal, a mobile terminal, a wireless terminal, a remote terminal, ahandset, a user agent, a mobile client, a client, or as some othersuitable term.

In order to reduce signaling overhead in LTE networks, the 3rdGeneration Partnership Project (3GPP) LTE specifications have definedSemi-Persistent Scheduling (SPS). SPS can be activated by an eNB and canbe applied to uplink (e.g., the UE is granted a transmission opportunityevery mth transmission time interval (TTI) until further notice) as wellas downlink (e.g., the UE expects to receive transmission from thenetwork every pth TTI further notice). This periodic time interval(e.g., m TTIs or p TTIs) may be referred to herein as a time-intervalparameter.

According to SPS, a resource is initially granted and then substantiallythe same resource is periodically used for subsequent data packets. Thatis, in SPS, the resource that an eNB provides for data packets on anuplink or downlink is allocated at regular intervals based on a grantand/or a single scheduling request (SR). An original grant of an SPSresource can be referred to as SPS activation. If, at a subsequent time,the eNB needs to reallocate an SPS resource with different parameters,the subsequent grant can be referred to as SPS reconfiguration.

An eNB typically grants an uplink or downlink resource to a UE bysending SPS activation/reconfiguration signaling to the user device overa control channel such as, for example, the physical downlink controlchannel (PDCCH) or enhanced PDCCH (ePDCCH). Among the data that the eNBmight include in the SPS activation/reconfiguration signaling are thesize of a resource block allocation (RBA), other parameters related tothe resource allocation, such as a modulation and coding scheme (MCS)that will be used for the resource, a time-interval parameter thatspecifies a periodic time interval between transmissions (uplink ordownlink, as applicable), etc.

An RBA may specify one or more resources (e.g., frequency and/or time)that may be used for communication by one or more devices of acommunication network. For example, in LTE, the smallest modulationstructure is a resource element. A resource element can be, for example,one 15 kHz subcarrier by one symbol. Resource elements can aggregateinto resource blocks. In general, a resource block has dimensions ofsubcarriers by symbols. In an example, twelve consecutive subcarriers inthe frequency domain and six or seven symbols in the time domain canform each resource block. In certain embodiments, a number of resourceblocks assigned to a given UE can constitute its resource blockallocation. In a typical embodiment, the MCS summarizes a modulationorder (e.g., binary phase-shift keying (BPSK), quadrature phase-shiftkeying (QPSK), etc.) and a coding rate (e.g., a number of bits that canbe transmitted in an allocated period of time). The coding rate can bedetermined as a function of the modulation order and the RBA. The MCScan be based on factors such as, for example, a channel qualityindication (CQI) received from the UE.

A maximum size of a data packet can be derived from the SPS parametersdescribed above. With SPS, scheduling signaling is generally only neededfor the initial transmission. Subsequent transmissions can reuse thesame scheduling decision as in the initial transmission and therebyavoid additional scheduling signaling. While SPS can help to reduce thesignaling overhead, there are some disadvantages when it is used forvoice traffic. A voice conversation alternates between talk spurts (whenthe user is talking) and silence intervals (when the user is listening).During a talk spurt, a speech packet may be issued by a vocoder every Nmilliseconds (ms). When the conversation transitions from a talk spurtto a silence interval, the vocoder may stop generating speech packetsand start generating comfort-noise packets, which are sent at a lowerperiodicity (e.g., every K ms, with K>N). For example, for vocodersimplementing Adaptive Multi-Rate (AMR) or Adaptive Multi-Rate Wideband(AMR-WB) codecs, it may be that K=160 and N=20.

In some embodiments, it may be advantageous to configure SPS with atime-interval parameter such that m=N during talk spurts and m=K duringsilence intervals. However, the eNB, and not the UE, typically makesscheduling decisions. At least with respect to uplink transmissions fromthe UE, the eNB is generally unaware of transitions from a talk spurt toa silence interval or from a silence interval to a talk spurt. Toconserve radio resources when, for example, the UE transitions from atalk spurt to a silence interval, uplink SPS can be configured to beimplicitly released when the UE transmits a certain number ofconsecutive empty packets (e.g., a media access control (MAC) protocoldata unit (PDU) with no MAC service data unit (SDU)). The certain numbercan be specified, for example, in an implicit-release parameter of theuplink SPS.

One option is to configure the implicit-release parameter with a lowvalue (e.g., 2) so that the uplink SPS is released easily. This optioncan result in significant signaling overhead. When another uplink packetneeds to be transmitted by the UE, a procedure to acquire uplinkresources is executed. The procedure can be similar to the following:(1) the UE sends a SR (2) the eNB provides an uplink grant; (3) the UEsends a Buffer Status Report (BSR) to indicate its resourcerequirements; (4) the eNB provides an uplink grant; and (5) the UE sendsthe uplink packet. After SPS implicit release, if no new uplink SPS isactivated, a similar procedure may be executed for every uplink packet.

Another option is to configure the implicit-release parameter with ahigh value so that the uplink SPS is released much less easily. However,resource waste can still result. Because transmission opportunities aremaintained on a periodic basis, when there is no uplink data to send, anempty packet is typically transmitted at each opportunity. For example,upon transition from a talk spurt to a silence interval, the UE maytransmit many empty packets without ever reaching the number ofconsecutive empty packets specified by the implicit-release parameter.The same scheduling decision that was made for the talk spurt remains ineffect even though such resources may no longer be needed. This optioncan also have other disadvantages such as unnecessarily causing UEbattery drain and increased interference.

In addition to lacking an ability to adjust the time-interval parameteras described above, the eNB is also not typically able to adjust SPS,uplink or downlink, to accommodate variable packet sizes such as, forexample, a set of non-uniformly-sized future packets. In general, apacket size can be a sum of a header size and a payload size.Packet-size fluctuation or changes can be caused by various factors thataffect the header size, the payload size, or both.

For example, relative to voice traffic, packet headers can be muchlarger than packet payload (e.g., on the order of 40-60 bytes forheaders and on the order of 20-50 bytes for payload). Robust headercompression (ROHC) as defined, for example, in IETF RFC 3095, can beused in the LTE Packet Data Convergence Protocol (PDCP) layer tocompress the packet headers before transmission over a radio interface.The size of the ROHC-compressed packet headers may fluctuate. By way offurther example, adaptive codecs such as AMR or AMR-WB may also change asize of packet payloads. One option for addressing fluctuating packetsizes is to assign, at the time of SPS activation, a transport blocksize larger than what is needed. A disadvantage of this option isinefficient utilization of radio resources.

Moreover, because a RBA and MCS remain the same at every TTI followingSPS activation, the eNB generally cannot adjust uplink SPS, for example,to changing radio-channel conditions. This can result in transmissionfailures and/or non-optimal radio-resource usage. One option to mitigatethe problem is for the eNB to assign, at the time of uplink SPSactivation, a more robust MCS than, for example, what is recommended bythe UE. While such a conservative approach might reduce a risk oftransmission failure, it fails to eliminate that risk and can result infar less efficient utilization of radio resources.

The present disclosure describes examples of facilitatingreconfiguration of both uplink SPS and downlink SPS after SPSactivation. In certain embodiments, the reconfiguration can occur inresponse to transitions from talk spurts to silence intervals,packet-size changes, radio conditions, and/or other factors. In manycases, the reconfiguration can occur via explicit signaling. In othercases, the reconfiguration can occur implicitly. Further, in certainembodiments, an eNB can improve downlink scheduling decisions byoptimizing when each UE sends status information such as can becontained within a channel status report (CSR).

I. Example of a Wireless Communication System for SPS Reconfiguration

FIG. 1 illustrates an example of a wireless communication system 100that can facilitate SPS reconfiguration. The system 100 includes a UE102 that communicates with an eNB 104 to access a wireless network. TheUE 102 can be a mobile terminal, a stationary terminal, a tethereddevice (such as a modem), a portion thereof, and/or the like. Moreover,the eNB 104 can be a macro node, femto node, pico node, micro node, orsimilar eNB, a relay node, a mobile base station, a UE (e.g.,communicating in peer-to-peer or ad-hoc mode with the UE 102), a portionthereof, and/or the like. In addition, the eNB 104 can facilitate UE 102communication with a core network (not shown) to receive wirelessnetwork services, such as packet-switched (PS) voice services includingvoice-over-internet protocol (VoIP), other data services, and/or thelike.

The UE 102 can include a voice receiving component 106 for obtainingaudio input (e.g., analog voice signals), a vocoder component 108 forgenerating digital voice data packets based on the input, a UE-sidescheduler component 110 for scheduling data communication with the eNB104 based on resources scheduled with the eNB 104, a transmittingcomponent 112 for communicating data packets to the eNB 104 overscheduled resources, a UE-side reconfiguration component 114 foridentifying SPS adjustments or modifications, a reporting component 116for generating and initiating transmission of CSRs, a UE-sidereconfiguration settings component 120 for establishing and/or storingSPS reconfiguration settings, and a ROHC component 122. The eNB 104includes an eNB-side reconfiguration component 118 for reconfiguringalready-active SPS and other functionality, an eNB-side schedulercomponent 124, and an eNB-side reconfiguration settings component 126for establishing and/or storing SPS reconfiguration settings.

According to an example, the voice receiving component 106 can obtainanalog audio signals for encoding. The analog signals, for example, caninclude analog voice signals received over a microphone or other inputdevice. The vocoder component 108 can generate digital data packets fromthe voice signals for communicating in a wireless network. In oneexample, the vocoder component 108 can generate the packets every 20milliseconds (ms). The vocoder component 108 can provide the packets toa lower layer for scheduling/transmission thereof. In variousembodiments, the vocoder component 108 can implement a codec such asAMR, AMR-WB, and/or the like.

The UE-side scheduler component 110 can receive resource assignmentsfrom the eNB 104 for communicating in the wireless network. Suchassignments can be received and/or requested according to certain timeintervals. The resource assignments can be established, for example, bythe eNB-side scheduler component 124. The UE-side scheduler component110, for example, can include a MAC layer scheduler.

The transmitting component 112 can transmit data, including the digitaldata packets generated by vocoder component 108, during the scheduledresource assignments. The transmitting component 112 can include aphysical layer transmit processor and/or related antenna(s). Thetransmitting component 112 can also include, for example, a MAC layertransmission component. Moreover, for example, the vocoder component 108can generate the data packets as a VoIP, voice-over-LTE (VoLTE) orsimilar packets for transmitting over the wireless network.

In one example, the eNB 104 can utilize dynamic scheduling to scheduleresources to the UE 102. Dynamic scheduling can be implemented invarious ways. As one example, the UE-side scheduler component 110 caninitially send a SR to the eNB 104 to notify of data to send at the UE102. The eNB 104 can then allocate resources for the UE 102 andcommunicate an indication of resources to the UE 102 in an uplink grant.The UE-side scheduler component 110 can then schedule data fortransmitting over the resources indicated in the uplink grant (e.g.,time and frequency) by the transmitting component 112.

The UE-side reconfiguration component 114 can monitor activity of thevoice receiving component 106, the vocoder 108, and the transmittingcomponent 112 and/or other components of the UE 102 for conditions orchanges that make reconfiguration of an already-active SPS appropriate.In certain embodiments, the monitoring can include detecting atransition from a talk spurt to a silence interval, a transition from asilence interval to a talk spurt, a packet-size fluctuation event (e.g.,as caused by ROHC and/or an adaptive codec), and/or the like.

In one example, based on the monitoring and/or other factors, theUE-side reconfiguration component 114 can identify one or moreadjustments or modifications to a configuration parameter of thealready-active uplink SPS. In some cases, the configuration parametermay relate to a packet-size profile supported by the RBA and MCS, atime-interval parameter, and/or the like. In certain embodiments, theUE-side reconfiguration component 114 can explicitly indicate theidentified adjustment or modification to the eNB 104 via an SPSreconfiguration request, implicitly indicate the identified adjustment,etc. Additional examples of operation of the UE-side reconfigurationcomponent 114 will be described in greater detail below with respect tothe ensuing Figures.

In certain embodiments, the UE-side reconfiguration settings component120 can establish and/or store reconfiguration settings in memory of theUE 102. The reconfiguration settings can relate, for example, to uplinkSPS and/or downlink SPS. Examples of reconfiguration settings that canbe established and/or stored by the UE-side reconfiguration settingscomponent 120 will be described in greater detail below. The ROHC 122can perform ROHC-related functionality as described above and in greaterdetail below with respect to FIGS. 2-2B.

The reporting component 116 can generate CSRs and initiate transmissionof the CSRs to the eNB 104 (e.g., on the Physical Uplink Control Channel(PUCCH) or another channel). Each CSR can include, for example, a CQIthat indicates a MCS recommended by the UE 102, a precoder matrixindication (PMI) that specifies a downlink precoder matrix recommendedby the UE 102, a rank indication (RI) that specifies a number of layersthat should be used for downlink transmission, and/or other suitableinformation. In some embodiments, the CSRs can assist the eNB 104 indownlink scheduling decisions such as, for example, what resource blocksand MCS to allocate to the UE 102. In many cases, the eNB 104 may followa latest recommendation from the UE 102. In other cases, the eNB 104 mayoverride the recommendation of the UE 102 based on other considerations.

In certain embodiments, the reporting component 116 can generate andinitiate transmission of CSRs at a periodic interval. As describedbelow, the eNB 104 may configure CSR parameters such as the periodicinterval, or periodicity, at which the UE 102 sends the CSR (e.g. sendevery N subframes) and an offset (e.g., start sending at subframe M). Incertain embodiments, the CSR parameters can be configured by the eNB 104using the radio resource control (RRC) protocol.

The eNB-side reconfiguration component 118 can monitor uplink data,downlink data, radio conditions, and/or other factors for conditions orchanges that make reconfiguration of an already-active SPS appropriate.In various embodiments, the eNB-side reconfiguration component 118 caninitiate reconfiguration of already-active uplink SPS and/oralready-active downlink SPS. In various embodiments, the eNB-sidereconfiguration component 118 can interact with the UE-sidereconfiguration component 114 on the UE 102 to receive and act on SPSreconfiguration requests. In addition, in various embodiments, theeNB-side reconfiguration component 118 can optimize the periodicinterval at which the UE 102 sends CSRs. Further examples of operationof the eNB-side reconfiguration component 118 will be described below.

In certain embodiments, the eNB-side reconfiguration settings component126 can establish and/or store reconfiguration settings in memory of theeNB 104. The reconfiguration settings can relate, for example, to uplinkSPS and/or downlink SPS. Examples of reconfiguration settings that canbe established and/or stored by the eNB-side reconfiguration settingscomponent 126 will be described in greater detail below.

II. Example of a VoIP Coding and Communicating Process

FIG. 2A illustrates an example VoIP coding and communicating process 200for a transmitter and receiver. In certain embodiments, the UE-sidereconfiguration component 114 can be resident on both the transmitterand the receiver. Each UE-side reconfiguration component 114 of FIG. 1is operable to monitor the process 200.

For example, a microphone 202 can receive analog voice signals over asampling interval and convert the analog signals to digital signals 204.Transmit pulse code modulation (PCM) post processing 206 can beperformed for the digital signals, and the signals can be encoded byencoder 208, which can be the vocoder 108, for example. Real-timetransport protocol (RTP) packetization 210 is performed to formulate theencoded signal into packets for transmitting in a wireless network. Thepackets can be provided to a user datagram protocol (UDP)/internetprotocol (IP) layer 212. ROHC 214 is optionally performed on the packets(e.g., by the ROHC component 122), and the packets can be transmittedover an LTE network 218 using an LTE transmitter 216 (e.g., via an eNBand other LTE network components).

The packets are received at LTE receiver 220, which can be at adifferent network entity, such as a UE. ROHC decompression 222 isperformed on the packets, and the packets are provided to UDP/IP layer224. RTP packetization 226 can process the packets to generate thecorresponding digital signal. The signal is provided to dejitter buffer228 to queue the signal for providing to upper layers sequentially withother signals. Decoder 230 decodes the VoIP signal, and receive PCM postprocessing 222 is performed to demodulate the signal. The signal isconverted from digital to an analog signal 234 and provided to a speakerat 236.

In certain embodiments, as part of monitoring the process 200, theUE-side reconfiguration component 114 can identify changes or conditionsthat may make adjustment to uplink SPS desirable. In one example, theUE-side reconfiguration component 114 detects transitions from a talkspurt to a silence interval and/or from a silence interval to a talkspurt. In another example, by monitoring output of the encoder 208, theUE-side reconfiguration component 114 may be able to identify acodec-related packet-fluctuation event. For example, AMR and AMR-WB mayadjust their rates from 4.75 kbps to 12.2 kbps and from 6.6 kbps to23.85 kbps, respectively. During silence intervals, these codecs maygenerate comfort-noise packets at a rate of about 1.8 kbps. The UE-sidereconfiguration component 114 can detect the rate adjustment as apacket-fluctuation event that affects a size of future uplink packets.

Another example involves ROHC. ROHC can be modeled as an interactionbetween two state machines, one at a compressor (e.g., the ROHC 214) andone at a decompressor (e.g., the ROHC 222). ROHC can include, forexample, three compressor states: Initialization and Refresh (IR), FirstOrder (FO), and Second Order (SO), by increasing order of compressionratio. In a typical embodiment, the compressor starts in the IR state,where it sends uncompressed headers. Subsequently, the compressor cantransition to a state of higher compression ratio when it is confidentthat the decompressor has the information necessary to decompress aheader compressed according to that higher state. Such confidence can beattained, for example, through ROHC acknowledgements (ACKs) from thedecompressor.

In general, the SO state reflects the state where a compression ratio ishighest. Compressed header sizes are generally near constant in the SOstate. Typically, once past the initialization stage of the IR state,the compressor may start a talk spurt in the FO state for a few packetsbefore transitioning to the SO state. For the remainder of the talkspurt, the compressor may occasionally revert to the FO state for a fewpackets and then return to the SO state. In the SO state, the compressormay send, for example, type-0 packets, which can have a compressedheader as small as 2 octets, assuming a 1-octet large cell ID (CID). Inthe FO state, the compressor may send, for example, type-1 and/or type-2packets, whose header size may be in the range of 2-3 octets. In the IRstate, the header may be roughly as large an uncompressed header (e.g.,40 to 60 octets).

ROHC can also include three modes: Unidirectional (U), Optimistic (O)and Reliable (R). In general, the U mode is designed for unidirectionalcommunication where there is no feedback channel. LTE and similarnetworks may be considered bidirectional. For purposes of providingexamples relative to LTE networks, the following description will focuson the O and R modes. In the R mode, the compressor relies on ROHC ACKsto be confident the decompressor has obtained the needed information todecompress headers compressed according to the next higher state, beforethe compressor transitions to that higher state.

In the O mode, the compressor assumes the decompressor has obtained theneeded information after a certain number of packets carrying theinformation have been transmitted. The compressor can also rely on theROHC ACKs. The ROHC ACKs may be considered part of the ROHC feedback,which feedback may be sent as standalone packets, piggybacked on packetswith actual payload for the opposite direction, etc. Assuming a 1-octetlarge CID, a given ROCH ACK may be, for example, as small as threeoctets. Feedback sizes may be, for example, in the range of a fewoctets.

In certain embodiments, as a result of the ROHC functionality describedabove, the ROHC header (which can include the compressed header and theROHC feedback, if piggybacked) may fluctuate and thereby cause packetsizes to fluctuate. In certain embodiments, the UE-side reconfigurationcomponent 114 can monitor the ROHC 214 and/or the ROHC 222 forpacket-size fluctuations according to the state.

FIG. 2B illustrates examples of R-mode and O-mode operations that can bedetected by the UE-side reconfiguration module 114 during, for example,the process 200. In a typical embodiment, the UE-side reconfigurationcomponent 114 is operable to detect a mode and compression state that isapplicable at a given time. To simplify discussion, FIG. 2B assumes thatno packet is sent during silence intervals.

In particular, FIG. 2B illustrates an R-mode initial talk spurt 252, anR-mode subsequent talk spurt 254, an O-mode initial talk spurt 256, andan O-mode subsequent talk spurt 258. The R-mode initial talk spurt 252,the R-mode subsequent talk spurt 254, the O-mode initial talk spurt 256,and the O-mode subsequent talk spurt 258 are examples of packet-sizepatterns that can form the basis for a packet-size profile. Once theR-mode initial talk spurt 252, the R-mode subsequent talk spurt 254, theO-mode initial talk spurt 256, and/or the O-mode subsequent talk spurt258 are detected by the UE-side reconfiguration module 114, SPSreconfiguration can be triggered according to a correspondingpacket-size profile.

In an example, during the R-mode initial talk spurt 252, the compressorstarts in the IR state and sends IR packet P1. Upon receiving an ACK,the compressor transitions to a higher compression state, which is theSO state in this example. In the SO state, the compressor sends R0packets. Periodically, the compressor may sendR0-Cyclic-Redundancy-Check (CRC) packets (e.g. P62), which packets thedecompressor is expected to acknowledge (e.g., ACK(P62)). After thecompressor receives the ACK, it may again send R0 packets. Continuingthis example, the compressor may start the R-mode subsequent talk spurt254 in the FO state and send UOR2 packet Pn. When Pn is acknowledged,the compressor may transition to the SO state (i.e., a higher compressorstate) and send R0 packets. As with the R-mode initial talk spurt 252,the compressor may periodically send R0-CRC packets (e.g., Pn+61), whichpackets the decompressor normally acknowledges (e.g., ACK(Pn+61)). Afterreceiving the ACK, the compressor may again send R0 packets.

In another example, during the O-mode initial talk spurt 256, thecompressor does not rely on ACKs from the decompressor but ratherassumes it can safely transition to a higher compression state aftersending three packets of the same type. For purposes of this example,P1, P2 and P3 are sent in the IR state. Thereafter, the compressortransitions to the SO state, where it sends type UO0 packets. During thesubsequent O-mode talk spurt 258, the compressor begins in the FO stateand sends three UOR2 packets, after which it transitions to the SO stateand sends UO0 packets.

III. Example of User Equipment

FIG. 3 illustrates a UE 300 that can facilitate SPS reconfiguration. Incertain embodiments, the UE 300 can operate as described with respect tothe UE 102 of FIG. 1. The UE 102 can include a receiver 302 thatreceives a signal from, for instance, a receive antenna (not shown),performs actions on (e.g., filters, amplifies, downconverts, etc.) thereceived signal, and digitizes the conditioned signal to obtain samples.The receiver 302 can include a demodulator 304 that can demodulatereceived symbols and provide them to a processor 306 for channelestimation. The processor 306 can be a processor dedicated to analyzinginformation received by receiver 302 and/or generating information fortransmission by a transmitter 308, a processor that controls one or morecomponents of the UE 300, and/or a processor that both analyzesinformation received by the receiver 302, generates information fortransmission by a transmitter 308, and controls one or more componentsof the UE 300.

The UE 300 can additionally include memory 310 that is operativelycoupled to the processor 306 and that can store data to be transmitted,received data, information related to available channels, dataassociated with analyzed signal and/or interference strength,information related to an assigned channel, power, rate, or the like,and any other suitable information for estimating a channel andcommunicating via the channel. The memory 310 can additionally storeprotocols and/or algorithms associated with estimating and/or utilizinga channel (e.g., performance based, capacity based, etc.).

It will be appreciated that the data store (e.g., memory 310) describedherein can be either volatile memory or nonvolatile memory, or caninclude both volatile and nonvolatile memory. By way of illustration,and not limitation, nonvolatile memory can include read only memory(ROM), programmable ROM (PROM), electrically programmable ROM (EPROM),electrically erasable PROM (EEPROM), or flash memory. Volatile memorycan include random access memory (RAM), which acts as external cachememory. By way of illustration and not limitation, RAM is available inmany forms such as synchronous RAM (SRAM), dynamic RAM (DRAM),synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhancedSDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM).The memory 310 of the subject systems and methods is intended toinclude, without being limited to, these and any other suitable types ofmemory.

The UE 300 further includes a modulator 322 that modulates signals fortransmission by the transmitter 308, for instance, to a base station,another UE, etc. For example, the transmitter 308 can transmit servingCIDs to a positioning server via one or more base stations, asdescribed, and can be similar to transmitting component 112. Moreover,for example, the UE 300 can include multiple transmitters 308 formultiple network interfaces.

IV. Example of an LTE Network Architecture

FIG. 4 is a diagram illustrating an LTE network architecture 400. TheLTE network architecture 400 may be referred to as an Evolved PacketSystem (EPS) 400. The EPS 400 may include one or more UE 402, an EvolvedUMTS Terrestrial Radio Access Network (E-UTRAN) 404, an Evolved PacketCore (EPC) 410, a Home Subscriber Server (HSS) 420, and an Operator's IPServices 422. In certain embodiments, the one or more UE 402 can operateas described with respect to the UE 102 and/or the UE 300.

The EPS 400 can interconnect with other access networks, but forsimplicity those entities/interfaces are not shown. The E-UTRAN 404includes an eNB 406 and other eNBs 408. In certain embodiments, the eNB406 and the other eNBs 408 can operate as described with respect to theeNB 104. The eNB 406 provides user and control planes protocolterminations toward the UE 402. The eNB 406 may be connected to theother eNBs 408 via an X2 interface (e.g., backhaul). The eNB 406provides an access point to the EPC 410 for the one or more UE 402.

The eNB 406 is connected by an S1 interface to the EPC 410. The EPC 410includes a Mobility Management Entity (MME) 412, other MMEs 414, aServing Gateway 416, and a Packet Data Network (PDN) Gateway 418. TheMME 412 is the control node that processes the signaling between the UE402 and the EPC 410. Generally, the MME 412 provides bearer andconnection management. All user IP packets are transferred through theServing Gateway 416, which itself is connected to the PDN Gateway 418.The PDN Gateway 418 provides UE IP address allocation as well as otherfunctions. The PDN Gateway 418 is connected to the Operator's IPServices 422. The Operator's IP Services 422 may include the Internet,the Intranet, an IP Multimedia Subsystem (IMS), and a PS StreamingService (PSS).

V. Example of a Radio Protocol Architecture

FIG. 5 is a diagram 500 illustrating an example of a radio protocolarchitecture for the user and control planes in LTE, which architecturecan be used to perform signaling related to SPS reconfiguration. Theradio protocol architecture for the UE and the eNB is shown with threelayers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowestlayer and implements various physical layer signal processing functions.The L1 layer will be referred to herein as the physical layer 506. Layer2 (L2 layer) 508 is above the physical layer 506 and is responsible forthe link between the UE and eNB (e.g., the UE 102 and the eNB 104) overthe physical layer 506.

In the user plane, the L2 layer 508 includes a MAC sublayer 510, a radiolink control (RLC) sublayer 512, and a PDCP sublayer 514, which areterminated at the eNB (e.g., the eNB 104) on the network side. Althoughnot shown, the UE (e.g., the UE 102) may have several upper layers abovethe L2 layer 508 including a network layer (e.g., IP layer) that isterminated at the PDN gateway 518 on the network side, and anapplication layer that is terminated at the other end of the connection(e.g., far end UE, server, etc.).

The PDCP sublayer 514 provides multiplexing between different radiobearers and logical channels. The PDCP sublayer 514 also provides headercompression (e.g., ROHC as described above) for upper layer data packetsto reduce radio transmission overhead, security by ciphering the datapackets, and handover support for UEs between eNBs. The RLC sublayer 512provides segmentation and reassembly of upper layer data packets,retransmission of lost data packets, and reordering of data packets tocompensate for out-of-order reception due to hybrid automatic repeatrequest (HARQ). The MAC sublayer 510 provides multiplexing betweenlogical and transport channels. The MAC sublayer 510 is also responsiblefor allocating the various radio resources (e.g., resource blocks) inone cell among the UEs. The MAC sublayer 510 is also responsible forHARQ retransmissions. HARQ error detection/correction can occur, forexample, at the physical layer 506 described above.

In the control plane, the radio protocol architecture for the UE and eNBis substantially the same for the physical layer 506 and the L2 layer508 with the exception that there is no header compression function forthe control plane. The control plane also includes a radio resourcecontrol (RRC) sublayer 516 in Layer 3 (L3 layer). The RRC sublayer 516is responsible for obtaining radio resources (e.g., radio bearers) andfor configuring the lower layers using RRC signaling between the eNB andthe UE.

VI. Example of eNB Communication with UE

FIG. 6 is a block diagram of an eNB 610 in communication with a UE 650in an access network. In certain embodiments, the eNB 610 can operate asdescribed with respect to the eNB 104 and/or the eNB 406. In certainembodiments, the UE 650 can operate as described with respect to the UE102, the UE 300, and/or the UE 402. In the downlink, upper layer packetsfrom the core network are provided to a controller/processor 675. Thecontroller/processor 675 implements the functionality of the L2 layer.In the downlink, the controller/processor 675 provides headercompression (e.g., ROHC), ciphering, packet segmentation and reordering,multiplexing between logical and transport channels, and radio resourceallocations to the UE 650 based on various priority metrics. Thecontroller/processor 675 is also responsible for HARQ operations,retransmission of lost packets, and signaling to the UE 650.

The transmit (TX) processor 616 implements various signal processingfunctions for the L1 layer (e.g., physical layer). The signal processingfunctions includes coding and interleaving to facilitate forward errorcorrection (FEC) at the UE 650 and mapping to signal constellationsbased on MCS (e.g., binary phase-shift keying (BPSK), quadraturephase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadratureamplitude modulation (M-QAM)). The coded and modulated symbols are thensplit into parallel streams. Each stream is then mapped to an OFDMsubcarrier, multiplexed with a reference signal (e.g., pilot) in thetime and/or frequency domain, and then combined together using anInverse Fast Fourier Transform (IFFT) to produce a physical channelcarrying a time domain OFDM symbol stream. The OFDM stream is spatiallyprecoded to produce multiple spatial streams. Channel estimates from achannel estimator 674 may be used to determine the MCS, as well as forspatial processing. The channel estimate may be derived from a referencesignal and/or channel condition feedback transmitted by the UE 650. Eachspatial stream is then provided to a different antenna 620 via aseparate transmitter 618TX. Each transmitter 618TX modulates an RFcarrier with a respective spatial stream for transmission.

At the UE 650, each receiver 654RX receives a signal through itsrespective antenna 652. Each receiver 654RX recovers informationmodulated onto an RF carrier and provides the information to the receive(RX) processor 656. The RX processor 656 implements various signalprocessing functions of the L1 layer. The RX processor 656 performsspatial processing on the information to recover any spatial streamsdestined for the UE 650. If multiple spatial streams are destined forthe UE 650, they may be combined by the RX processor 656 into a singleOFDM symbol stream. The RX processor 656 then converts the OFDM symbolstream from the time-domain to the frequency domain using a Fast FourierTransform (FFT). The frequency domain signal comprises a separate OFDMsymbol stream for each subcarrier of the OFDM signal. The symbols oneach subcarrier, and the reference signal, is recovered and demodulatedby determining the most likely signal constellation points transmittedby the eNB 610. These soft decisions may be based on channel estimatescomputed by the channel estimator 658. The soft decisions are thendecoded and deinterleaved to recover the data and control signals thatwere originally transmitted by the eNB 610 on the physical channel. Thedata and control signals are then provided to the controller/processor659.

The controller/processor 659 implements the L2 layer. Thecontroller/processor can be associated with a memory 660 that storesprogram codes and data. The memory 660 may be referred to as acomputer-readable medium. In the uplink, the control/processor 659provides demultiplexing between transport and logical channels, packetreassembly, deciphering, header decompression, control signal processingto recover upper layer packets from the core network. The upper layerpackets are then provided to a data sink 662, which represents all theprotocol layers above the L2 layer. Various control signals may also beprovided to the data sink 662 for L3 processing. Thecontroller/processor 659 is also responsible for error detection usingan ACK and/or negative acknowledgement (NACK) protocol to support HARQoperations.

In the uplink, a data source 667 is used to provide upper layer packetsto the controller/processor 659. The data source 667 represents allprotocol layers above the L2 layer. Similar to the functionalitydescribed in connection with the downlink transmission by the eNB 610,the controller/processor 659 implements the L2 layer for the user planeand the control plane by providing header compression, ciphering, packetsegmentation and reordering, and multiplexing between logical andtransport channels based on radio resource allocations by the eNB 610.The controller/processor 659 is also responsible for HARQ operations,retransmission of lost packets, and signaling to the eNB 610.

Channel estimates derived by a channel estimator 658 from a referencesignal or feedback transmitted by the eNB 610 may be used by the TXprocessor 668 to select the appropriate MCS and to facilitate spatialprocessing. The spatial streams generated by the TX processor 668 areprovided to different antenna 652 via separate transmitters 654TX. Eachtransmitter 654TX modulates an RF carrier with a respective spatialstream for transmission.

The uplink transmission is processed at the eNB 610 in a manner similarto that described in connection with the receiver function at the UE650. Each receiver 618RX receives a signal through its respectiveantenna 620. Each receiver 618RX recovers information modulated onto anRF carrier and provides the information to a RX processor 670. The RXprocessor 670 may implement the L1 layer.

The controller/processor 675 implements the L2 layer. Thecontroller/processor 675 can be associated with a memory 676 that storesprogram codes and data. The memory 676 may be referred to as acomputer-readable medium. In the uplink, the control/processor 675provides demultiplexing between transport and logical channels, packetreassembly, deciphering, header decompression, control signal processingto recover upper layer packets from the UE 650. Upper layer packets fromthe controller/processor 675 may be provided to the core network. Thecontroller/processor 675 is also responsible for error detection usingan ACK and/or NACK protocol to support HARQ operations.

VII. Example of a Process for SPS Reconfiguration

FIG. 7 illustrates an example of a process 700 for performing uplink SPSreconfiguration. The process 700 can be implemented by any system thatcan process data and send/receive signals. For example, the process 700,in whole or in part, can be implemented by one or more of the UE 102,the eNB 104, the UE 300, the UE 402, the eNB 406, the UE-side schedulercomponent 110, the UE-side reconfiguration component 114, the UE-sidereconfiguration settings component 120, the eNB-side reconfigurationcomponent 118, and/or the eNB-side reconfiguration settings component126. The process 700 can also be performed generally by the wirelesscommunication system 100. Although any number of systems, in whole or inpart, can implement the process 700, to simplify discussion, the process700 will be described in relation to the UE 102 and/or the eNB 104, asappropriate.

At block 702, uplink SPS is activated. In certain embodiments, theuplink SPS can be activated via, for example, two signaling steps.First, the eNB 104 can send an SPS configuration to the UE 102 via RRCsignaling (e.g., at the RRC sublayer 516). Second, the eNB 104 can sendscheduling signaling (e.g., downlink control information (DCI) format 0)on a control channel (e.g., PDCCH, ePDCCH, etc.). The schedulinginformation can include, for example, a RBA and an MCS. In someembodiments, to indicate that this is not a regular DCI format 0 butrather one for SPS, the signaling can be addressed to an SPS Cell RadioNetwork Temporary Identifier (C-RNTI) of the UE 102 using, for example,specific bit patterns. A first SPS uplink transmission can be specifiedto begin at subframe n. The uplink SPS can include, for example, theparameters listed in Table 1 below.

TABLE 1 Parameter Description Time-Interval Parameter Interval betweenthe periodic (“semiPersistSchedIntervalUL”) transmission opportunities,in units of TTIs. m is set to this parameter value Implicit-ReleaseParameter If there has been no uplink (“implicitReleaseAfter”) data(empty packets) after implicitReleaseAfter transmission opportunities,the SPS is released.

At block 704, the UE 102 identifies a proposed adjustment to one or moreconfiguration parameters of the uplink SPS. The configuration parametercan be a time-interval parameter, an implicit-release parameter, apacket size accommodated by the RBA and the MCS, and/or the like. Incertain embodiments, the block 704 can include monitoring a VoIP codingand communicating process such as the process 200 for atalk-spurt-to-silence-interval transition, asilence-interval-to-talk-spurt transition, a packet-size fluctuationevent (e.g., a packet-size change due to a codec-related event or aROHC), etc. In some cases, the proposed adjustment can be based onpredicted fluctuations or interval changes (e.g., based on a detectedtransition). In other cases, the proposed adjustment can be based on adetected (e.g., observed) fluctuation, interval change, etc.

At block 706, the UE 102 performs signaling sufficient to indicate arequest for reconfiguration to the eNB 104. More particularly, therequest can include information sufficient to identify the proposedadjustment. In some cases, the request can be indicated via explicitsignaling. Examples of explicit signaling will be described in greaterdetail with respect to FIGS. 8-15C.

As indicated in Table 2 below, in various embodiments, the request mayinclude information sufficient to identify a proposed time-intervalparameter, a packet-size profile, a proposed starting subframe for theSPS reconfiguration, a combination of same, and/or the like. In atypical embodiment, the proposed starting subframe can be defined interms of an offset. For example, a starting subframe can be specified asStarting_SF_UL+Last_subframe, where Last_subframe is either: (a) thesubframe where the last uplink SPS transmission was sent, ifSPS_Reconfig_Request is not sent as part of an uplink SPS transmission;or (b) the subframe where the SPS_Reconflg_Request is sent, ifSPS_Reconfig_Request is sent as part of an uplink SPS transmission.

TABLE 2 Example Elements of an SPS Reconfiguration Request(“SPS_Reconfig_Request”) Proposed Time-Interval Parameter(“New_semiPersistSchedIntervalUL”) Packet-Size Profile (“Size_Profile”)Starting Subframe (“Starting_SF_UL”)

In certain embodiments, by including a proposed time-interval parameteras part of an SPS reconfiguration request, the UE 102 can request theeNB 104 to reconfigure the uplink SPS with a new value for the intervalbetween periodic uplink transmissions. In various embodiments, theproposed time-interval parameter may result from a transition from atalk spurt to a silence interval, a transition from a silence intervalto a talk spurt, a change in operation by a vocoder such as the vocoder108, and/or the like.

In certain embodiments, by including a packet-size profile as part of anuplink SPS reconfiguration request, the UE 102 can request the eNB 104to adjust a scheduling decision so that sizes of upcoming packets Pn,Pn+1, Pn+2, etc. can be accommodated. Adjusting the scheduling decisioncan include adjusting a RBA, MCS, etc. In general, a packet-size profilecan include information indicative of a size of each of one or morefuture uplink packets (e.g., Pn, Pn+1, Pn+2, etc.). In some cases, agiven packet-size profile may include a single value to be applied, forexample, to all packets Pn, Pn+1, Pn+2, etc. In other cases, morecomplex profiles can specify different values for each of the packetsPn, Pn+1, Pn+2, etc. In these cases, non-uniformly-sized future uplinkpackets can be efficiently accommodated. As elaborated on below, thepacket-size profile may result from a transition from a talk spurt to asilence interval, ROHC, adaptive codecs, and/or the like.

In an example, with reference to FIG. 2B, a packet-size profilecorresponding to the O-mode subsequent talk spurt 258 could include asize of a first three packets in an upcoming talk spurt (UOR2 packets),and a size of subsequent packets (UO0 packets). In another example, alsowith reference to FIG. 2B, a packet-size profile corresponding to theR-mode initial talk spurt 252 could include a size of IR packets, and asize of subsequent packets (R0 packets), with the exception that every61st packet is a R0-CRC packet and can have a corresponding specifiedsize.

For a given SPS reconfiguration request, a time-interval parameter, apacket-size profile, and/or a starting subframe can be encoded invarious ways. For example, each can be expressly indicated via values,indirectly indicated by indices to a corresponding preconfigured arrayor table, and/or the like. Examples will be described in greater detailbelow.

At block 708, the eNB 104 optionally determines whether to reconfigurethe uplink SPS. As part of the block 708, the eNB 104 may check that theproposed adjustment complies, for example, with bearer QoS attributesand/or other considerations. In some cases, the eNB 104 may determine tomake an adjustment specified by the request for reconfiguration. Inother cases, the eNB 104 may determine not to make any adjustment. Instill other cases, the eNB 104 may determine to make a differentadjustment from the adjustment specified by the request forreconfiguration. In some embodiments, the block 708 can be omitted. Inthese embodiments, the process 700 may proceed directly from block 706to block 712.

At decision block 710, if the eNB 104 determines to reconfigure, theprocess 700 proceeds to block 712. Otherwise, the process 700 proceedsto block 718. At block 718, in some embodiments, the eNB 104 may notifythe UE 102 of the no-reconfiguration determination. In other cases, theblock 718 can be omitted such that the process 700 ends after theno-reconfiguration determination.

At block 712, the eNB 104 reconfigures the uplink SPS as determined atthe block 708. At block 714, the eNB 104 notifies the UE 102 of thereconfigured uplink SPS. At block 716, the UE 102 and the eNB 104implement the reconfigured uplink SPS. For example, the UE 102 maytransmit uplink packets to the eNB 104 according to the reconfigureduplink SPS.

VIII. Examples of SPS Reconfiguration Settings

Further examples of content that can be included in an SPSreconfiguration request will now be described. In some embodiments, atime-interval parameter, a size profile, and a starting subframe asdescribed above can each be encoded as indices to an array. Forinstance, reconfiguration settings can be established that include anarray of time-interval-parameter values (e.g.,New_semiPersistSchedIntervalUL[i], for i=0 to Length −1), an array ofsize profiles (e.g., Size_Profile[i], for i=0 to Length −1), an array ofstarting subframes (e.g., Starting_SF_UL[i], for i=−0 to Length −1),and/or the like. The UE 102 and the eNB 104 can each be configured withthe reconfiguration settings so that it is possible to exchange arrayindices instead of actual values. In various embodiments, the exchangeof indices can further improve the efficiency of communication betweenthe UE 102 and the eNB 104.

For simplicity of description, the examples described below assume thatthe vocoder 108 uses the AMR or AMR-WB codec and that ROHC is utilized.For the AMR and AMR-WB codecs, the periodicity intervals are assumed tobe 160 ms and 20 ms for comfort noise and talk spurts, respectively. Forpurposes of ROHC, the following additional assumptions are made:

(1) An initial talk spurt starts with an IR packet having 50 bytes ofspeech and an IR header for a total of 90 bytes for IPv4 and 110 bytesfor IPv6.

(2) A subsequent talk spurt starts with UOR2 packets having 50 bytes ofspeech and 3 bytes of compressed header for a total of 53 bytes.

(3) A subsequent silence interval starts with UOR2 packets having 5bytes of comfort noise and 3 bytes of compressed header for a total of 8bytes.

(4) In the higher compression state of a talk spurt, the compressorsends R0 or UO0 packets both of size 52 bytes. In the R mode,occasionally, R0-CRC packets of size 53 bytes are sent.

(5) In the higher compression state of a silence interval, thecompressor sends R0 or UO0 packets both of size 7 bytes. In the R mode,occasionally, R0-CRC packets of size 8 bytes are sent; and

(6) The compressor transitions to a higher compression state aftertransmitting one or three packets of the same type, depending on theparticular example.

A. Example Reconfiguration Settings for a Time-Interval Parameter

Table 3 below illustrates an example of reconfiguration settings for atime-interval parameter. Specifically, Table 3 illustrates an array oflength two such that an index of zero corresponds to a value of 20 msand an index of one corresponds to a value of 160 ms. In an example, theindex of zero can relate to a talk spurt while the index of one canrelate to a silence interval.

TABLE 3 New_semiPersistSchedIntervalUL Index (in ms)semiPersistSchedIntervalUL [0] 20 semiPersistSchedlntervalUL [1] 160

In certain embodiments, when both the UE 102 and the eNB 104 have thereconfiguration settings shown in Table 3, a request for SPSreconfiguration from the UE 102 can specify an index (i.e., one or zero)corresponding to its proposed adjustment of the time-interval parameter.For example, upon a detected transition from a talk spurt to a silenceinterval, the UE 102 may send to the eNB 104 an SPS reconfigurationrequest that specifies an index of one. In similar fashion, upon adetected transition from a silence interval to a talk spurt, the UE 102may send to the eNB 104 an SPS reconfiguration request that specifies anindex of zero.

B. Example Reconfiguration Settings for a Starting Subframe

Table 4 below illustrates an example of reconfiguration settings for astarting subframe (e.g., in terms of an offset from a last subframe asdescribed above). Specifically, Table 4 illustrates an array of lengthtwo such that an index of zero corresponds to a value of 20 ms and anindex of one corresponds to a value of 60 ms. In an example, the indexof zero can relate to a talk spurt while the index of one can relate toa silence interval.

TABLE 4 Starting_SF_UL Index (in ms) Starting_SF_UL[0] 20Starting_SF_UL[1] 60

In certain embodiments, when both the UE 102 and the eNB 104 have thereconfiguration settings shown in Table 4, a request for SPSreconfiguration from the UE 102 can specify an index (i.e., one or zero)corresponding to its proposed starting subframe. For example, upon adetected transition from a talk spurt to a silence interval, the UE 102may send to the eNB 104 an SPS reconfiguration request that specifies anindex of one. In similar fashion, upon a detected transition from asilence interval to a talk spurt, the UE 102 may send to the eNB 104 anSPS reconfiguration request that specifies an index of zero.

C. Example Reconfiguration Settings for a Size Profile

Table 5 below illustrates an example of reconfiguration settings for asize profile. Specifically, Table 5 illustrates an array of two sizeprofiles. For example, an index of zero can relate to a size profilesuch that a first three packets are of size 8 bytes and all subsequentpackets are of size 7 bytes until further notice. In certainembodiments, the index of zero can be applicable to a silence intervalin the O mode. Similarly, an index of one can mean that a first threepackets are of size 53 bytes while all subsequent packets are of size 52bytes until further notice.

TABLE 5 Size_Profile Index (in bytes) Size_Profile [0] 8, 8, 8, 7*Size_Profile [1] 53, 53, 53, 52*

Table 6 illustrates another example of reconfiguration settings for asize profile. According to this example, an index of zero can relate toa size profile such that a first upcoming packet is of size 53 bytes,subsequent packets are of size 52 bytes, and every 61^(st) packet is ofsize 53 bytes. In certain embodiments, the index of one can beapplicable to a talk spurt in the R mode.

TABLE 6 Size_Profile Index (in bytes) Size_Profile [0] 8, 7*, 8+, 61Size_Profile [1] 53, 52*, 53+, 61

D. Example of Scaled Encoding for Size Profiles

Table 7 illustrates an example of scaled encoding of size profiles.According to this example, an index can be used to specify a range ofsizes rather than specific exact sizes. For example, an index of two cancorrespond to 20<Size<=35, an index of four can correspond to40<Size<=50, etc. In many cases, the example size-profilereconfiguration settings described above can be expressed in terms ofthe scaled encoding of Table 7. For instance, the Size_Profile[0] ofTable 6 can be expressed as index zero of Table 7. Likewise, theSize_Profile[1] of Table 6 can be expressed as Size_Profile[5] of Table7.

TABLE 7 Range of Sizes Index (in bytes) Size_Profile [0]  0 < Size <= 10Size_Profile [1] 10 < Size <= 20 Size_Profile [2] 20 < Size <= 35Size_Profile [3] 35 < Size <= 40 Size_Profile [4] 40 < Size <= 50Size_Profile [5] 50 < Size <= 60 . . .

E. Example of Configuration Profiles (Tuples)

In certain embodiments, reconfiguration settings can include an array ofconfiguration profiles. In these embodiments, each configuration profilecan be a tuple that includes, for example, a time-parameter value, asize profile, a starting subframe, and/or other configurations (e.g.,Config_Profile[i]=(New_semiPersisiSchedIntervalUL, Size_Profile.Starting_SF_UL), for i=0 to (M−1)). In that way, a single index can beused to reference the tuple.

Table 8 below illustrates an example of reconfiguration settings thatcan include an array of configuration profiles. In some embodiments, thearray of configuration profiles shown in Table 8 can be used during theO mode described above. Examples utilizing Table 8 will be describedwith respect to FIGS. 15A-15C.

TABLE 8 New_semiPer- sistSchedIntervalUL Size_Profile Starting_SF_ULIndex (in ms) (in bytes) (in ms) ConfigProfile[0] 160 8, 8, 60 8, 7*ConfigProfile[1] 20 53, 53, 20 53, 52* ConfigProfile[2] 20 90, 90, 2090, 52* ConfigProfile[3] 160 8, 8, 0 8, 7*

Table 9 below illustrates another example of reconfiguration settingsthat can include an array of configuration profiles. In someembodiments, the array of configuration profiles shown in Table 9 can beused during the R mode described above

TABLE 9 New_semiPer- sistSchedIntervalUL Size_Profile Starting_SF_ULIndex (in ms) (in bytes) (in bytes) ConfigProfile [0] 160 8, 7*, 60 8+,61 ConfigProfile [1] 20 53, 52*, 20 53+, 61 ConfigProfile [2] 20 90,52*, 20 53+, 61 ConfigProfile [3] 160 8, 7*, 0 8+, 61

IX. Examples of Overrides

In various embodiments, the UE 102 can be permitted to override SPS fora defined number of next packet transmissions. In some cases, the UE 102may request to override an already-active SPS. In other cases, the UE102 may request SPS reconfiguration that includes an override for acertain initial number of packets. Other examples will be apparent toone skilled in the art after reviewing the present disclosure.

Table 10 illustrates an example of elements that an SPS reconfigurationrequest can include for purposes of requesting override of a currentpacket-size profile accommodated by uplink SPS. In particular, overridesize of Override_Size can be requested for Number_of_Overrides packettransmissions. After Number_of_Overrides packet transmissions, anotherwise applicable size profile again becomes effective. In someembodiments, it may be requested that the override apply until furthernotice, for example, by setting the Number_of_Overrides to zero.

TABLE 10 SPS Reconfiguration Request Element Description Override_SizeSize of upcoming packet(s), for example, in bytes. Number_of_OverridesThe Override_Size applies to the next Number_of_Overrides packettransmissions.

To illustrate the override approach, the example of Table 8 is nowencoded as shown in Table 11. Size overrides can be used with respect toTable 11 in order to attain results equivalent to those of Table 8. Forexample, the UE 102 can send an SPS reconfiguration request withindex=1, Override_Size=90, and Number_of_Overrides=3. This can achievethe same result as ConfigProfile[2] of Table 8.

TABLE 11 New_semiPer- sistSchedIntervalUL Size_Profile Starting_SF_ULIndex (in ms) (in bytes) (in ms) ConfigProfile [0] 160 7 60ConfigProfile [1] 20 52 20 ConfigProfile [3] 160 7 0

To further illustrate the override approach, the example of Table 9 isnow encoded as shown below in Table 12. Size overrides can be used withrespect to Table 12 in order to attain results equivalent to those ofTable 9. For example, at the start of an initial talk spurt, the UE 102can send an SPS reconfiguration request with index=1, Override_Size=90,Number_of_Overrides=1. For the remainder of the initial talk spurt, theUE 102 can send an SPS reconfiguration request with Override_Size=53 andNumber_of_Overrides=1 every 61^(st) packet. This can achieve the sameresult as ConfigProfile[2] of Table 9.

TABLE 12 New_semiPer- sistSchedIntervalUL Size_Profile Starting_SF_ULIndex (in ms) (in bytes) (in ms) 0 160 7 60 1 20 52 20 3 160 7 0

At the start of a subsequent talk spurt, the UE 102 can send an SPSreconfiguration request with index=1, Override_Size=53, andNumber_of_Overrides=1. For the remainder of the subsequent talk spurt,the UE can send an SPS reconfiguration request with Override_Size=53 andNumber_of_Overrides=1 every 61^(st) packet. This can achieve the sameresult as ConfigProfile[1] of Table 9.

At the start of a silence interval with comfort noise, the UE 102 cansend an SPS reconfiguration request with an index value of 0 or 3,depending whether a first comfort-noise packet has already beentransmitted. In either case, the SPS reconfiguration request can specifyOverride_Size=8 and Number_of_Overrides=1. For the remainder of thesilence interval, the UE 102 can transmit an SPS reconfiguration requestwith Override_Size=8 and Number_of_Overrides=1 at every 61st packet. Incases where the first comfort-noise packet has not yet been transmitted,this functionality can achieve the same result as ConfigProfile[0] ofTable 9. In cases where the first comfort-noise packet has already beentransmitted, this functionality can achieve the same result asConfigProfile[3] of Table 9.

In certain embodiments, size overrides can be used to accommodatenumerous types of packet-size fluctuations in addition to thosedescribed above. In an example, the UE 102 could request a size overridewhenever detecting a need to send uplink data at a volume higher thancan be accommodated by a current RBA and MCS. Size overrides can also beadvantageous when used with non-voice packets. For example, sizeoverrides can be requested to accommodate web browsing on the UE 102.

It should be appreciated that, in various embodiments, size profiles canalso be specified to account for packet-size fluctuations or changescaused by other events and conditions not expressly described above. Forexample, in an embodiment, size profiles can be specified to account forpiggybacked ROHC feedbacks. Scaled encoding as described above can alsobe derived to address such circumstances.

In addition, it should be appreciated that a size profile such as thosedescribed above are generally usable by the eNB 104 to determine a RBAand a MCS. In certain embodiments, a granularity of size profiles can betailored according to packet sizes that might merit a different RBAand/or MCS. For instance, in the example of Table 12 above for asubsequent talk spurt (index=1), the UE 102 may not need to request asize override every 61^(st) packet if the RBA is not expected to changerelative to an uplink packet of size 53 bytes.

X. Examples of Uplink SPS Reconfiguration

FIG. 8 illustrates a signaling timeline 800 for uplink SPSreconfiguration. For illustrative purposes, the signaling timeline 800uses a reserved bit R that can be found, for example, in a MAC header ofevery uplink packet (e.g., at the MAC sublayer 510 of FIG. 5). Thereserved bit R is typically set to zero in LTE specifications. Incertain embodiments, the UE 102 can implicitly request an uplink grantby giving the reserved bit R a value of one.

At 8-S1, the UE 102 transmits an uplink packet to the eNB 104 using analready-active uplink SPS. As shown, the reserved bit R is set to zeroin the uplink packet. At 8-S2, the UE 102 transmits another uplinkpacket to the eNB 104 in accordance with the uplink SPS; however, thereserved bit R is set to one. In certain embodiments, the reserved bit Rbeing set to one can correspond to an implicit request for an uplinkgrant. At 8-S3, the eNB 104 allocates an uplink grant to the UE 102.

At 8-S4, according to the uplink grant, the UE 102 sends an SPSreconfiguration request, for example, as a MAC control element of anuplink packet. In general, the SPS reconfiguration request can includeany of the example content described above such as actual values,indices to arrays, size overrides, etc. After verifying the SPSreconfiguration request as described, for example, with respect toblocks 708-710 of FIG. 7, at 8-S5, the eNB 104 sends schedulingsignaling (e.g., DCI format 0) on a control channel such as, forexample, PDCCH or ePDCCH.

The scheduling signaling can include, for example, new parameters asrequested in the SPS reconfiguration request. In some embodiments,rather than sending the scheduling signaling over the control channel,the eNB 104 can send an ACK (e.g., SPS_Reconfig_Ack) as a MAC controlelement. At 8-S6 and 8-S7, the UE 102 transmits uplink packets accordingto the reconfigured uplink SPS.

FIG. 9 illustrates a signaling timeline 900 for uplink SPSreconfiguration. For illustrative purposes, the signaling timeline 900uses a reserved bit R that can be found, for example, in a MAC header ofevery uplink packet (e.g., at the MAC sublayer 510 of FIG. 5). Thereserved bit R is typically set to zero in LTE specifications. Incertain embodiments, the UE 102 can implicitly request an uplink grantby giving the reserved bit R a value of one.

At 9-S1, the UE 102 transmits an uplink packet of size X to the eNB 104using an already-active uplink SPS. As shown, the reserved bit R is setto zero in the uplink packet. At 9-S2, the UE 102 transmits anotheruplink packet of size X to the eNB 104 in accordance with the uplinkSPS; however, the reserved bit R is set to one. In certain embodiments,the reserved bit R being set to one can correspond to an implicitrequest for an uplink grant. At 9-S3, the eNB 104 allocates an uplinkgrant to the UE 102.

At 9-S4, according to the uplink grant, the UE 102 sends an SPSreconfiguration request, for example, as a MAC control element of anuplink packet. According to this example, the SPS reconfigurationrequest indicates a packet size of Y for future uplink packets. Invarious embodiments, the request can include a packet profile specifyingthe packet size of Y, an index to such a packet profile, etc. Ingeneral, the SPS reconfiguration request can include any of the examplecontent described above such as actual values, indices to arrays, sizeoverrides, etc.

After verifying the SPS reconfiguration request as described, forexample, with respect to blocks 708-710 of FIG. 7, at 9-S5, the eNB 104sends scheduling signaling (e.g., DCI format 0) on a control channelsuch as, for example, PDCCH or ePDCCH. The scheduling signaling caninclude, for example, new parameters as requested in the SPSreconfiguration request. In some embodiments, rather than sending thescheduling signaling over the control channel, the eNB 104 can send anACK (e.g., SPS_Reconfig_Ack) as a MAC control element.

At 9-S6 and 9-S7, the UE 102 transmits uplink packets of size Y to theeNB 104 according to the reconfigured uplink SPS. For subsequentpackets, the eNB 104 may send scheduling signaling as needed. In manycases, the applicable size profile may specify a set ofnon-uniformly-sized future uplink packets, some of which may requiremore or fewer RBs. For example, at 9-S8, the eNB 104 can send schedulingsignaling indicative of additional SPS reconfiguration to accommodate apacket size of Z. At 9-S9, the UE 102 transmits an uplink packet of sizeZ to the eNB 104 according to the additional SPS reconfiguration.

FIG. 10 illustrates a signaling timeline 1000 for uplink SPSreconfiguration. In particular, FIG. 10 depicts an example of includingan SPS reconfiguration request as a MAC control element. At 10-S1, theUE 102 transmits an uplink packet to the eNB 104 using an already-activeuplink SPS. At 10-S2, the UE 102 transmits an SPS reconfigurationrequest to the eNB 104. According to this example, the SPSreconfiguration request is transmitted at a regularly scheduled TTIaccording to a time-interval parameter of the already-active uplink SPS.

After verifying the SPS reconfiguration request as described, forexample, with respect to blocks 708-710 of FIG. 7, at 10-S3, the eNB 104sends scheduling signaling (e.g., DCI format 0) on a control channelsuch as, for example, PDCCH or ePDCCH. The scheduling signaling caninclude, for example, new parameters as requested in the SPSreconfiguration request. In some embodiments, rather than sending thescheduling signaling over the control channel, the eNB 104 can send anACK (e.g., SPS_Reconfig_Ack) as a MAC control element. At 10-S4 and10-S5, the UE 102 transmits uplink packets according to the reconfigureduplink SPS.

FIG. 11 illustrates a signaling timeline 1100 for uplink SPSreconfiguration. Like FIG. 10, FIG. 11 depicts an example of includingan SPS reconfiguration request as a MAC control element. The example ofFIG. 11 specifically relates to a reconfiguration that includespacket-size reconfiguration. At 11-S1, the UE 102 transmits an uplinkpacket of packet size X to the eNB 104 using an already-active uplinkSPS.

At 11-S2, the UE 102 transmits another uplink packet of size X to theeNB 104. According to this example, the uplink packet of 11-S2 includesan SPS reconfiguration request as a MAC control element. The uplinkpacket of 11-S2 is transmitted at a regularly scheduled TTI according toa time-interval parameter of the already-active uplink SPS. According tothis example, the SPS reconfiguration request indicates a packet size ofY for future uplink packets. In various embodiments, the request caninclude a packet profile specifying the packet size of Y, an index tosuch a packet profile, etc. In general, the SPS reconfiguration requestcan include any of the example content described above such as actualvalues, indices to arrays, size overrides, etc.

After verifying the SPS reconfiguration request as described, forexample, with respect to blocks 708-710 of FIG. 7, at 11-S3, the eNB 104sends scheduling signaling (e.g., DCI format 0) on a control channelsuch as, for example, PDCCH or ePDCCH. The scheduling signaling caninclude, for example, new parameters as requested in the SPSreconfiguration request. In some embodiments, rather than sending thescheduling signaling over the control channel, the eNB 104 can send anACK (e.g., SPS_Reconfig_Ack) as a MAC control element.

At 11-S4 and 11-S5, the UE 102 transmits uplink packets of size Y to theeNB 104 according to the reconfigured uplink SPS. For subsequentpackets, the eNB 104 may send scheduling signaling as needed. In manycases, the applicable size profile may specify a set ofnon-uniformly-sized future uplink packets, some of which may requiremore or fewer RBs. For example, at 11-S6, the eNB 104 can sendscheduling signaling indicative of additional SPS reconfiguration toaccommodate a packet size of Z. At 11-S7, the UE 102 transmits an uplinkpacket of size Z to the eNB 104 according to the additional SPSreconfiguration.

FIG. 12 illustrates a signaling timeline 1200 for uplink SPSreconfiguration. In particular, FIG. 12 depicts an example of using a SRto obtain an uplink grant for an SPS reconfiguration request. Theexample of FIG. 12 specifically relates to a reconfiguration thatincludes packet-size reconfiguration. At 12-S1, the UE 102 transmits anuplink packet of size X to the eNB 104 using an already-active uplinkSPS. At 12-S2, the UE 102 transmits a SR to the eNB 104.

At 12-S3, the eNB 104 allocates an uplink grant to the UE 102 inresponse to the SR. At 12-S4, according to the uplink grant, the UE 102sends an SPS reconfiguration request, for example, as a MAC controlelement of an uplink packet. According to this example, the SPSreconfiguration request indicates a packet size of Y for future uplinkpackets. In various embodiments, the request can include a packetprofile specifying the packet size of Y, an index to such a packetprofile, etc. In general, the SPS reconfiguration request can includeany of the example content described above such as actual values,indices to arrays, size overrides, etc.

After verifying the SPS reconfiguration request as described, forexample, with respect to blocks 708-710 of FIG. 7, at 12-S5, the eNB 104sends scheduling signaling (e.g., DCI format 0) on a control channelsuch as, for example, PDCCH or ePDCCH. The scheduling signaling caninclude, for example, new parameters as requested in the SPSreconfiguration request. In some embodiments, rather than sending thescheduling signaling over the control channel, the eNB 104 can send anACK (e.g., SPS_Reconfig_Ack) as a MAC control element.

At 12-S6 and 12-S7, the UE 102 transmits uplink packets of size Y to theeNB 104 according to the reconfigured uplink SPS. For subsequentpackets, the eNB 104 may send scheduling signaling as needed. In manycases, the applicable size profile may specify a set ofnon-uniformly-sized future uplink packets, some of which may requiremore or fewer RBs. For example, at 12-S8, the eNB 104 can sendscheduling signaling indicative of additional SPS reconfiguration toaccommodate a packet size of Z. At 12-S9, the UE 102 transmits an uplinkpacket of size Z to the eNB 104 according to the additional SPSreconfiguration.

FIG. 13 illustrates a signaling timeline 1300 for uplink SPSreconfiguration. More specifically, FIG. 13 illustrates an example ofperforming SPS reconfiguration by toggling between two reconfigurationsettings or sets of reconfiguration settings. The reconfigurationsettings can be, for example, two configuration profiles, twoalternative reconfiguration settings for a time-interval parameter, twoalternative packet-size profiles, and/or the like. In certainembodiments, the toggling can be initiated responsive to a detectedtransition from a talk spurt to a silence interval, a detectedtransition from a silence interval to a talk spurt, etc.

In certain embodiments, the UE 102 can signal a toggling, for example,in a current uplink packet according to already-active uplink SPS. Theexample of FIG. 13 uses a reserved bit R that can be found, for example,in a MAC header of every uplink packet (e.g., at the MAC sublayer 510 ofFIG. 5). The reserved bit R is typically set to zero in LTEspecifications. In certain embodiments, the UE 102 can signal a togglingby setting the reserved bit R to one.

At 13-S1, the UE 102 transmits an uplink packet to the eNB 104 using analready-active uplink SPS. As shown, the reserved bit R is set to zeroin the uplink packet. At 13-S2, the UE 102 transmits another uplinkpacket to the eNB 104 in accordance with the uplink SPS; however, thereserved bit R is now set to one. In certain embodiments, the reservedbit R being set to one can correspond to a toggle indicator. In otherwords, the toggle indicator can be considered an SPS reconfigurationrequest. For example, the toggle indicator may be indicative of atransition from a talk spurt to silence interval, a transition from asilence interval to a talk spurt, and/or the like.

After verifying the SPS reconfiguration request as described, forexample, with respect to blocks 708-710 of FIG. 7, at 13-S3, the eNB 104sends scheduling signaling (e.g., DCI format 0) on a control channelsuch as, for example, PDCCH or ePDCCH. The scheduling signaling caninclude, for example, new parameters that correspond to alternativesettings or an alternative profile (i.e., as requested via the toggleindicator). In some embodiments, rather than sending the schedulingsignaling over the control channel, the eNB 104 can send an ACK (e.g.,SPS_Reconfig_Ack) as a MAC control element. At 13-S4 and 13-S5, the UE102 transmits uplink packets according to the reconfigured uplink SPS.

FIG. 14 illustrates an example 1400 of using the reserved bit R toidentify reconfiguration settings. In similar fashion to the example ofFIG. 13, the example 1400 relates to performing SPS reconfiguration whenthere are two reconfiguration settings or sets of reconfigurationsettings. The reconfiguration settings can be, for example, twoconfiguration profiles, two alternative reconfiguration settings for atime-interval parameter, two alternative packet-size profiles, and/orthe like. Differently from the example of FIG. 13, however, FIG. 14depicts utilization of the reserved bit R to identify an index value ofreconfiguration settings or a set of reconfiguration settings thatshould be applicable.

Specifically, the example 1400 includes a timeline 1402, a timeline1404, and a timeline 1406. The timeline 1402 illustrates an example of atransition from a talk spurt to a silence interval. At each uplinktransmission, the UE 102 can indicate an index value (e.g., 0 or 1) thatcorresponds to a reconfiguration setting or set of reconfigurationsettings that should be applicable. Therefore, the reserved bit R can bemeaningful with each uplink transmission. For example, as illustrated inthe timeline 1402, a value of zero can correspond to an index value fora talk spurt. Similarly, a value of one can correspond to an index valuefor a silence interval. In the timeline 1402, when the UE 102 transmitsan uplink packet such that R equals one, a transition to the silenceinterval can be indicated and the eNB 104 can initiate uplink SPSreconfiguration and corresponding scheduling signaling in the fashiondescribed above.

In a similar manner, the timelines 1404 and 1406 illustrate transitionsfrom a silence interval to a talk spurt. Thus, R is set to one duringeach uplink transmission of the talk spurt. As shown in the timeline1404, in some embodiments, the UE 102 can initiate SPS reconfigurationby requesting, for example, an uplink grant and setting the reserved bitR appropriately in a next uplink packet. The timeline 1404 can beadvantageous, for example, if there is no scheduled transmissionopportunity when the talk spurt starts. In other embodiments, as shownin the timeline 1406, the UE 102 can set the reserved bit Rappropriately at a next scheduled transmission opportunity. The timeline1406 can be beneficial, for example, if there is a scheduledtransmission opportunity sufficiently close to when the talk spurtstarts.

FIGS. 15A-15C illustrate examples of SPS reconfiguration using SPSreconfiguration settings as shown below in Table 13. It should beappreciated that the content of Table 13 is identical to that of Table 8above.

TABLE 13 New_semiPer- sistSchedIntervalUL Size_Profile Starting_SF_ULIndex (in ms) (in bytes) (in ms) ConfigProfile[0] 160 8, 8, 60 8, 7*ConfigProfile[1] 20 53, 53, 20 53, 52* ConfigProfile[2] 20 90, 90, 2090, 52* ConfigProfile[3] 160 8, 8, 0 8, 7*

FIG. 15A illustrates SPS reconfiguration for an initial talk spurt 1502and a subsequent talk spurt 1504. For purposes of the example of FIG.15A, it can be assumed that at least one silence interval occurs betweenthe initial talk spurt 1502 and the subsequent talk spurt 1504.

At a start of the initial talk spurt 1502, or at a time just before thestart, the UE 102 acquires uplink resources (e.g., an uplink grant) andtransmits an SPS reconfiguration request to the eNB 104. With referenceto Table 13 above, the SPS reconfiguration request specifies an indexvalue of two. According to this example, the index value of two fromTable 13 corresponds to a talk spurt that begins with IR packets (as isthe case with the initial talk spurt 1502).

At a start of the subsequent talk spurt 1504, or at a time just beforethe start, the UE 102 acquires uplink resources (e.g., an uplink grant)and transmits a second SPS reconfiguration request to the eNB 104. Withreference to Table 13 above, the second SPS reconfiguration requestspecifies an index value of one. According to this example, the indexvalue of one from Table 13 corresponds to a talk spurt that begins withtype UOR2 packets (as is the case with the subsequent talk spurt 1504).

FIG. 15B illustrates SPS reconfiguration for a silence interval 1506.FIG. 15B depicts a scenario in which the UE-side reconfigurationcomponent 114 is aware of the silence interval 1506 from the very firstpacket thereof (e.g., first comfort-noise packet). In some embodiments,the vocoder 108 may give the UE-side reconfiguration component 114advance notice of the silence interval 1506. At a start of the silenceinterval 1506, or just before the start, the UE 102 acquires uplinkresources (e.g., an uplink grant) and transmits an SPS reconfigurationrequest to the eNB 104. With reference to Table 13 above, the SPSreconfiguration request specifies an index value of zero, which indexvalue corresponds to an interval beginning with a first packet of thesilence interval 1506.

FIG. 15C illustrates SPS reconfiguration for a silence interval 1508. Inparticular, FIG. 15C depicts a scenario in which the UE-sidereconfiguration component 114 is not aware of the silence interval 1508from the very first packet. In some embodiments, the vocoder 108 may notgive the UE-side reconfiguration component 114 advance notice of thesilence interval 1508. In these embodiments, the UE-side reconfigurationcomponent 114 may infer the silence interval 1508, for example, afterthe transmission of two empty packets. After detecting the silenceinterval 1508, the UE 102 acquires uplink resources (e.g., an uplinkgrant) and transmits an SPS reconfiguration request to the eNB 104. Withreference to Table 13 above, the SPS reconfiguration request can specifyan index value of three, which index value corresponds to an intervalthat begins with a subsequent packet (e.g., a second packet) of thesilence interval 1508.

It should be appreciated that, in some cases, a codec implemented by thevocoder 108 may not transmit comfort-noise packets during silenceintervals. In such cases, when the UE 102 sends an SPS reconfigurationrequest responsive to a talk-spurt-to-silence-interval transition, theeNB 104 may elect to explicitly release an uplink SPS. According to thisexample, the UE 102 can initiate SPS activation upon transition to asubsequent talk spurt.

XI. Examples of Establishing Uplink SPS Reconfiguration Settings

In certain embodiments, uplinks SPS reconfiguration settings such as,for example, those settings described above with respect to Tables 3-12,can be established by the UE 102, the eNB 104, a combination thereof,and/or the like. For illustrative purposes, examples will be providedbelow relative to UE 102 and the eNB 104.

FIG. 16 illustrates an example of a process 1600 for UE establishment ofSPS reconfiguration settings. The process 1600 can be implemented by anysystem that can process data and send/receive signals. For example, theprocess 1600, in whole or in part, can be implemented by one or more ofthe UE 102, the eNB 104, the UE 300, the UE 402, the eNB 406, theUE-side scheduler component 110, the UE-side reconfiguration component114, the UE-side reconfiguration settings component 120, the eNB-sidereconfiguration component 118, and/or the eNB-side reconfigurationsettings component 126. The process 1600 can also be performed generallyby the wireless communication system 100. Although any number ofsystems, in whole or in part, can implement the process 1600, tosimplify discussion, the process 1600 will be described in relation tothe UE 102 and/or the eNB 104, as appropriate.

At block 1602, the UE 102 determines uplink SPS reconfigurationsettings. For example, in various embodiments, the UE-sidereconfiguration component 114 can monitor time intervals, packet sizes,and transition spacing at an output of vocoder (e.g., the encoder 208 orthe vocoder 108) as described with respect to FIGS. 1-2. The UE 102 canalso monitor an output of an ROHC compressor or ROHC decompressor (e.g.,the ROHC 214 or the ROHC 222 of FIG. 2). In certain embodiments, theUE-side reconfiguration component 114 can receive some of the uplink SPSreconfiguration settings, for example, from the vocoder, the ROHCcompressor, or another suitable component. The uplink SPSreconfiguration settings can be similar to those described above, forexample, with respect to Tables 3-12.

At block 1604, the UE 102 transmits the uplink SPS reconfigurationsettings to the eNB 104. At block 1606, the eNB 104 receives the uplinkSPS reconfiguration settings. At block 1608, the eNB 104 optionallyverifies the uplink SPS reconfiguration settings. In certainembodiments, the block 1608 can include performing functionality similarto the functionality described with respect to blocks 708-712 of FIG. 7.In certain embodiments, the block 1608 may be omitted. In theseembodiments, the process 1600 may proceed directly from block 1606 to1610 without any requirement of successful verification.

At block 1610, responsive to successful verification, the eNB 104transmits acceptance of the uplink SPS reconfiguration settings to theUE 102. At block 1612, the UE 102 receives the acceptance. At block1614, the UE 102 and the eNB 104 store the uplink SPS reconfigurationsettings, for example, in respective memory thereof. At block 1618, theUE 102 and the eNB 104 implement the uplink SPS reconfiguration settingsas needed, for example, by performing corresponding functionality uponthe occurrence of an appropriate transition or event.

FIG. 17 illustrates an example of a signaling timeline 1700 foraccomplishing transfer of uplink SPS reconfiguration settings from a UEto an eNB. For illustrative purposes, the signaling timeline 1700 willbe described relative to the UE 102 and the eNB 104 of FIG. 1. Invarious embodiments, operations depicted in the signaling timeline 1700may be performed as at least part of the process 1600 of FIG. 16.

At 17-S1, the UE 102 sends uplink SPS reconfiguration settings to theeNB 104. For example, the uplink SPS reconfiguration settings can besent in a new MAC control element (e.g., SPS_Config_Info). In certainembodiments, the new MAC control element can be identified by a logicalchannel ID (LCID) value assigned from one of a set of reserved LCIDvalues (e.g., “01100”). After verifying the uplink SPS reconfigurationsettings, for example, as described with respect to block 1608 of FIG.16, at 17-S2, the eNB 104 transmits an acceptance of the uplink SPSreconfiguration settings. The acceptance can be, for example, a new MACcontrol element (e.g., SPS_Config_Info_Accept). In certain embodiments,the new MAC control element can be identified by a new LCID value (e.g.,“01101”). Subsequently, the UE 102 can send an SPS reconfigurationrequest to transition from one SPS configuration to another as describedin detail above.

FIG. 18 illustrates an example of a signaling timeline 1800 foraccomplishing transfer of uplink SPS reconfiguration settings from a UEto an eNB using RRC signaling (e.g., at the RRC sublayer 516). Forillustrative purposes, the signaling timeline 1800 will be describedrelative to the UE 102 and the eNB 104 of FIG. 1. In variousembodiments, operations depicted in the signaling timeline 1800 may beperformed as at least part of the process 1600 of FIG. 16.

At 18-S1, the eNB 104 transmits to UE 102 a RRC connectionreconfiguration that includes information related to an active uplinkSPS. At 18-S2, the UE 102 replies, for example, with a “RRC ConnectionReconfiguration Complete” message, which message can include the uplinkSPS reconfiguration settings. After verifying the uplink SPSreconfiguration settings, for example, as described with respect toblock 1608 of FIG. 16, at 18-S3, the eNB 104 transmits, for example, a“RRC Connection Confirm” message. Subsequently, the UE 102 can send anSPS reconfiguration request to transition from one SPS configuration toanother as described in detail above.

FIG. 19 illustrates an example of a process 1900 for eNB establishmentof uplink SPS reconfiguration settings. The process 1900 can beimplemented by any system that can process data and send/receivesignals. For example, the process 1900, in whole or in part, can beimplemented by one or more of the UE 102, the eNB 104, the UE 300, theUE 402, the eNB 406, the UE-side scheduler component 110, the UE-sidereconfiguration component 114, the UE-side reconfiguration settingscomponent 120, the eNB-side reconfiguration component 118, and/or theeNB-side reconfiguration settings component 126. The process 1900 canalso be performed generally by the wireless communication system 100.Although any number of systems, in whole or in part, can implement theprocess 1900, to simplify discussion, the process 1900 will be describedin relation to the UE 102 and/or the eNB 104, as appropriate.

At block 1902, the eNB 104 determines uplink SPS reconfigurationsettings. In an example, the uplink SPS reconfiguration settings can bepreconfigured on the eNB 104 based on known values for the most commonlyexpected codecs and/or expected ROHC implementation behavior. Forexample, in certain embodiments, the values in Table 8 above can be usedassuming an AMR or AMR-WB codec and ROHC. In another example, the eNB104 can determine the uplink SPS reconfiguration settings by observingintervals, packet sizes, transition spacing, and/or othercharacteristics of uplink transmissions from the UE 102. According tothis example, the uplink SPS reconfiguration settings can be inferred.In another example, the uplink SPS reconfiguration settings can bedetermined by the eNB 104, for example, at bearer setup. In certainembodiments, from an IP version (e.g., v4 or v6) of the bearer, the eNBcan determine a size of part of the static context. Bearer-level QoSattributes communicated to the eNB 104 at bearer setup can be enhancedto include the uplink SPS reconfiguration settings.

At block 1904, the eNB 104 transmits the uplink SPS reconfigurationsettings to the UE 102. In one example, the uplink SPS reconfigurationsettings can be transmitted to the UE 102 via RRC signaling at a time ofuplink SPS activation (e.g., at block 702 of FIG. 7). Another examplewill be described with respect to FIG. 20.

At block 1906, the UE 102 receives the uplink SPS reconfigurationsettings. At block 1908, the UE 102 and the eNB 104 store the uplink SPSreconfiguration settings, for example, in respective memory thereof. Atblock 1910, the UE 102 and the eNB 104 implement the uplink SPSreconfiguration settings as needed, for example, by performingcorresponding functionality upon the occurrence of an appropriatetransition or event.

FIG. 20 illustrates an example of a signaling timeline 2000 foraccomplishing transfer of uplink SPS reconfiguration settings from aneNB to a UE. For illustrative purposes, the signaling timeline 2000 willbe described relative to the UE 102 and the eNB 104 of FIG. 1. Invarious embodiments, operations depicted in the signaling timeline 2000may be performed as at least part of the process 1900 of FIG. 19.

At 20-S1, the eNB 104 sends uplink SPS reconfiguration settings to theUE 102. For example, the uplink SPS reconfiguration settings can be sentin a new MAC control element (e.g., SPS_Config_Info). In certainembodiments, the new MAC control element can be identified by a LCIDvalue assigned from one of a set of reserved LCID values (e.g. “01100”).At 20-S2, the UE 102 transmits an acceptance of the uplink SPSreconfiguration settings. The acceptance can be, for example, a new MACcontrol element (e.g., SPS_Config_Info_Accept). In certain embodiments,the new MAC control element can be identified by a new LCID value (e.g.,“01101”). Subsequently, the UE 102 can send an SPS reconfigurationrequest to transition from one SPS configuration to another as describedin detail above.

XII. Examples of Implicit Uplink SPS Reconfiguration

In certain embodiments, uplink SPS can be designed to be implicitlyreconfigured when a UE such as the UE 102 triggers anSPS-reconfiguration event. In an example, the implicit-reconfigurationevent can be triggered by the UE 102 transmitting a certain number ofconsecutive empty packets (e.g., a MAC PDU with no MAC SDU). Particularcriteria for the SPS-reconfiguration event (e.g., the certain number ofempty packets) can be specified in an implicit-reconfiguration parameterof the uplink SPS. In various embodiments, the implicit-reconfigurationevent can be associated with a set of SPS reconfiguration settings(e.g., a configuration profile as described above). In general, theassociated reconfiguration settings can be similar to those describedwith respect to Tables 3-12. In that way, a preconfigured adjustment canoccur when the UE 102 triggers the SPS-reconfiguration event.

In an example, a silence-interval configuration profile can beassociated with a SPS-reconfiguration event. If the SPS-reconfigurationevent is triggered by transmitting a certain number of empty packets asdescribed above, upon a detected transition from a talk spurt to asilence interval, the UE 102 can unambiguously indicate to the eNB 104both the transition and a desired SPS reconfiguration by transmittingthe certain number of consecutive empty packets (i.e., in itstransmission opportunities). According to this example, the eNB 104 candetect the transmission of the certain number of empty packets as atrigger of the SPS-reconfiguration event and optionally reconfigure theuplink SPS according to the silence-interval configuration profile.Additional examples will be described below with respect to FIGS. 21-22.

FIG. 21 illustrates an example of a process 2100 for performing implicituplink SPS reconfiguration. The process 2100 can be implemented by anysystem that can process data and send/receive signals. For example, theprocess 2100, in whole or in part, can be implemented by one or more ofthe UE 102, the eNB 104, the UE 300, the UE 402, the eNB 406, theUE-side scheduler component 110, the UE-side reconfiguration component114, the UE-side reconfiguration settings component 120, the eNB-sidereconfiguration component 118, and/or the eNB-side reconfigurationsettings component 126. The process 2100 can also be performed generallyby the wireless communication system 100. Although any number ofsystems, in whole or in part, can implement the process 2100, tosimplify discussion, the process 2100 will be described in relation tothe UE 102 and/or the eNB 104, as appropriate.

At block 2102, uplink SPS is activated. In certain embodiments, theuplink SPS can be activated via, for example, two signaling steps.First, the eNB 104 can send an SPS configuration to the UE 102 via RRCsignaling (e.g., at the RRC sublayer 516). Second, the eNB 104 can sendscheduling signaling (e.g., downlink control information (DCI) format 0)on a control channel (e.g., PDCCH, ePDCCH, etc.). The schedulinginformation can include, for example, a RBA and an MCS. In someembodiments, to indicate that this is not a regular DCI format 0 butrather one for SPS, the signaling can be addressed to an SPS Cell RadioNetwork Temporary Identifier (C-RNTI) of the UE 102 using, for example,specific bit patterns. A first SPS uplink transmission can be specifiedto begin at subframe n. The uplink SPS can include, for example, theparameters listed in Table 14 below.

TABLE 14 Parameter Description Time-Interval Parameter Interval betweenthe periodic (“semiPersistSchedIntervalUL”) transmission opportunities,in units of TTIs. m is set to this parameter value Implicit-ReleaseParameter If there has been no uplink data (“implicitReleaseAfter”)(e.g., only empty packets) after implicitReleaseAfter transmissionopportunities, the SPS is released. Implicit-Reconfiguration ParameterIf there has been no uplink data (“implicitReconfigurationAfter”) (e.g.,only empty packets) after implicitReconfigurationAfter transmissionopportunities, the SPS is reconfigured in a preconfigured manner.

In particular, Table 14 illustrates inclusion of animplicit-reconfiguration parameter in the uplink SPS. In general, theimplicit-reconfiguration parameter can define a trigger for anSPS-reconfiguration event. For example, the implicit-reconfigurationparameter can specify a certain number of consecutive empty packets asdescribed above. In a typical embodiment, the implicit-reconfigurationparameter is associated with a set of reconfiguration settings (e.g., aconfiguration profile for a silence interval). In certain embodiments,the set of reconfiguration settings can be determined and exchanged inany manner described above with respect to FIGS. 16-20.

At block 2104, the UE 102 identifies a proposed adjustment to aconfiguration parameter of the uplink SPS. The block 2104 can generallyinclude performing any of the functionality described above with respectto block 704 of FIG. 7. For example, the UE 102 may identify atransition from a talk spurt to a silence interval. At block 2106, theUE 102 transmits the certain number of empty packets (e.g., one or more)to trigger the SPS-reconfiguration event. At block 2108, the eNB 104detects the trigger. As described above, the SPS-reconfiguration eventis associated with a preconfigured adjustment contained withinreconfiguration settings.

At block 2110, the eNB 104 optionally determines whether to reconfigurethe uplink SPS. As part of the block 2110, the eNB 104 may check thatthe preconfigured adjustment complies, for example, with bearer qualityof service (QoS) attributes and/or other policy considerations. In somecases, the eNB 104 may determine to make the preconfigured adjustment.In other cases, the eNB 104 may determine not to make any adjustment. Instill other cases, the eNB 104 may determine to make a differentadjustment from the preconfigured adjustment. In some embodiments, theblock 2110 is optional. In these embodiments, the process 2100 mayproceed directly from block 2108 to block 2114.

At decision block 2112, if the eNB 104 determines to reconfigure, theprocess 2100 proceeds to block 2114. Otherwise, the process 2100proceeds to block 2120. At block 2120, in some embodiments, the eNB 104may notify the UE 102 of the no-reconfiguration determination. In othercases, the block 2120 can be omitted such that the process 2100 endsafter the no-reconfiguration determination.

At block 2114, the eNB 104 reconfigures the uplink SPS as determined atthe block 2110. At block 2116, the eNB 104 notifies the UE 102 of thereconfigured uplink SPS via, for example, scheduling signaling asdescribed above. At block 2118, the UE 102 and the eNB 104 implement thereconfigured uplink SPS. For example, the UE 102 may transmit uplinkpackets to the eNB 104 according to the reconfigured uplink SPS.

FIG. 22 illustrates an example of a timeline 2202 for implicitreconfiguration of uplink SPS. The timeline 2202 depicts a transitionfrom a talk spurt to a silence interval in the fashion described above.For purposes of illustration, the timeline 2202 assumes that animplicit-reconfiguration parameter of an active uplink SPS is set totwo. As shown, after transmission of two empty packets by a UE such asthe UE 102, the active uplink SPS is implicitly reconfigured via aprocess similar to the process 2100 of FIG. 21. For example, an eNB suchas the eNB 104 can perform a preconfigured adjustment for the silenceinterval. The preconfigured adjustment can be contained withinreconfiguration settings (e.g., a configuration profile) as describedabove.

XIII. Examples of Uplink SPS Reconfiguration Combinations

It should be appreciated that various embodiments of uplink SPSreconfiguration as described above can be combined. In an example, at atransition instance in which the UE 102 would like to reconfigure basedon one of two alternative sets of reconfiguration settings (e.g.,configuration profiles), toggling as described with respect to FIG. 13can be used. As an alternative, in some embodiments, index signalingusing a reserved bit R as described with respect to FIG. 14 can be used.As another alternative, in some embodiments, implicit uplink SPSreconfiguration can be initiated as described with respect to FIG. 21(e.g., for a transition from a talk spurt to a silence interval).According to this example, if the UE 102 would like to reconfigure theSPS differently than specified, for example, in the two alternative setsof reconfiguration settings, explicit signaling to indicate a differentset of reconfiguration settings can be used. Alternatively, the UE 102can explicitly indicate actual values, for example, for a time-intervalparameter, a packet-size profile, and/or a starting subframe, in an SPSreconfiguration request as described above.

By way of illustration, assume that the vocoder 108 implements theAMR-WB codec such that semiPersistSchedIntervalUL_0=20 andsemiPersistSchedIntervalUL_1=160. In transitions from talk spurts tosilence intervals, the transitional spacing may be, for example, either60 ms or 160 ms. In a first case, the UE 102 may be informed via theAMR-WB codec of the occurrence of a first comfort-noise packet. In asecond case, the UE 102 itself may determine, for example, via theUE-side reconfiguration component, the start of a silence intervalwithout assistance from the AMR-WB codec. In the first case, a defaultvalue for Starting_SF_UL may be 60. In the second case, a default valuefor Starting_SF_UL is 160. In either case, in certain embodiments, thevalue of Starting_SF_UL does not need to be explicitly signaled whentransitioning from talk spurts to silence intervals.

XIV. Example of Downlink SPS Reconfiguration

In various embodiments downlink SPS reconfiguration can occur in amanner similar to that described above with respect to uplink SPSreconfiguration. Examples will be described below.

FIG. 23 illustrates an example of a process 2300 for performing downlinkSPS reconfiguration. The process 2300 can be implemented by any systemthat can process data and send/receive signals. For example, the process2300, in whole or in part, can be implemented by one or more of the UE102, the eNB 104, the UE 300, the UE 402, the eNB 406, the UE-sidescheduler component 110, the UE-side reconfiguration component 114, theUE-side reconfiguration settings component 120, the eNB-sidereconfiguration component 118, and/or the eNB-side reconfigurationsettings component 126. The process 2300 can also be performed generallyby the wireless communication system 100. Although any number ofsystems, in whole or in part, can implement the process 2300, tosimplify discussion, the process 2300 will be described in relation tothe UE 102 and/or the eNB 104, as appropriate.

At block 2302, downlink SPS is activated. In certain embodiments, thedownlink SPS can be activated via, for example, two signaling steps.First, the eNB 104 can send an SPS configuration to the UE 102 via RRCsignaling (e.g., at the RRC sublayer 516). Second, the eNB 104 can sendscheduling signaling (e.g., downlink control information (DCI) format 0)on a control channel (e.g., PDCCH, ePDCCH, etc.). The schedulinginformation can include, for example, a RBA and an MCS. In someembodiments, to indicate that this is not a regular DCI format 0 butrather one for SPS, the signaling can be addressed to an SPS Cell RadioNetwork Temporary Identifier (C-RNTI) of the UE 102 using, for example,specific bit patterns. A first SPS downlink transmission can bespecified to begin at subframe n. The downlink SPS can include, forexample, a time-interval parameter (e.g., semiPersistSchedIntervalDL).

At block 2304, the eNB 104 determines to reconfigure the downlink SPS.In typical embodiments, the block 2304 involves the eNB 104 identifyingan adjustment to one or more configuration parameters of the downlinkSPS. The configuration parameter can be a time-interval parameter, apacket size accommodated by the RBA and the MCS, and/or the like. Incertain embodiments, the block 2304 can include the eNB 104 monitoring aVoIP coding and communicating process such as the process 200 forintervals, packet sizes, and transition spacing of downlinktransmissions.

At block 2306, the eNB 104 performs signaling sufficient to indicate areconfigured downlink SPS to the UE 102. In particular, the signalingcan include information sufficient to identify the adjustment. Invarious embodiments, the request may include information sufficient toidentify a new time-interval parameter, a new packet-size profile, astarting subframe for the SPS reconfiguration, a combination of same,and/or the like.

In general, the new time-interval parameter, the new packet-sizeprofile, and/or the starting subframe can be expressed in any formdescribed above with respect to uplink SPS reconfiguration. For example,each can be expressly indicated via values, indirectly indicted byindices to a corresponding preconfigured array or table, and/or thelike. More particularly, each can be represented in downlink SPSreconfiguration settings that are similar to uplink SPS reconfigurationsettings described above with respect to Tables 3-12. Additionally,downlink SPS reconfiguration settings can be established and exchangedas described above with respect to uplink SPS reconfiguration settings(see description of FIGS. 16-20).

At block 2308, the UE 102 identifies the reconfigured downlink SPSbased, at least in part, on the signaling. The block 2308 can includethe UE 102 accessing downlink reconfiguration settings stored in memorythereof. At block 2310, the UE 102 and the eNB 104 implement thereconfigured downlink SPS. For example, the eNB 104 may transmitdownlink packets to the UE 102 according to the reconfigured downlinkSPS.

XV. Example of CSR Optimization

In certain embodiments, an eNB such as the eNB 104 can improve downlinkscheduling decisions by optimizing when each UE such as the UE 102 sendsa CSR. Each CSR can include, for example, a CQI that indicates a MCSrecommended by the UE, a PMI that specifies a downlink precoder matrixrecommended by the UE, a RI that specifies a number of layers thatshould be used for downlink transmission, and/or other suitableinformation. In some embodiments, the CSRs can assist the eNB 104 indownlink scheduling decisions such as, for example, what resource blocksand MCS to allocate to the UE 102. In many cases, the eNB 104 may followa latest recommendation from the UE 102. In other cases, the eNB 104 mayoverride the recommendation of the UE 102 based on other considerations.

In certain embodiments, the reporting component 116 can generate andinitiate transmission of CSRs at a periodic interval. As describedbelow, the eNB 104 may configure CSR parameters such as the periodicinterval, or periodicity, at which the UE 102 sends the CSR (e.g. sendevery N subframes) and an offset (e. g. start sending at subframe M). Incertain embodiments, the CSR parameters can be configured by the eNB 104using the radio resource control (RRC) protocol. More particularly, theeNB 104 can instruct the reporting component 116 of the UE 102 to send aCSR a preconfigured time before a scheduled downlink transmission. Incertain embodiments, the eNB 104 can reconfigure the CSR parameters eachtime downlink SPS configuration results in a modified time-intervalparameter. In this fashion, the eNB 104 can minimize wasted CSRs andensure that latest possible information is available before eachdownlink transmission.

FIG. 24 illustrates an example of a process 2400 for performing CSRoptimization. The process 2400 can be implemented by any system that canprocess data and send/receive signals. For example, the process 2400, inwhole or in part, can be implemented by one or more of the UE 102, theeNB 104, the UE 300, the UE 402, the eNB 406, the UE-side schedulercomponent 110, the UE-side reconfiguration component 114, the UE-sidereconfiguration settings component 120, the eNB-side reconfigurationcomponent 118, and/or the eNB-side reconfiguration settings component126. The process 2400 can also be performed generally by the wirelesscommunication system 100. Although any number of systems, in whole or inpart, can implement the process 2400, to simplify discussion, theprocess 2400 will be described in relation to the UE 102 and/or the eNB104, as appropriate.

At block 2402, the eNB 104 determines one or more times when the UE 102should send a CSR based, at least in part, on a modified time-intervalparameter. In various embodiments, the modified time interval parametermay be a result of a process such as the process 2300. In certainembodiments, the block 2402 can include determining a CSR configurationthat can include CSR parameters such as a periodic interval, orperiodicity, at which the UE 102 sends the CSR (e.g., send every Nsubframes) and an offset (e.g., start sending at subframe M). In anexample, the eNB 104 may configure the periodic interval and the offsetsuch that: (a) a single CSR will be transmitted by the UE 102 per timeinterval; and (b) the single CSR will arrive a configurable time beforea next downlink packet to the UE 102 (e.g., r subframes before subframeq, 1 subframe before subframe q, etc.).

At block 2404, the eNB 104 transmits information sufficient for the UE102 to identify the determined one or more times. For example, in someembodiments, the eNB 104 may transmit a CSR configuration to the UE 102.At block 2406, the UE 102 receives the information. At block 2408, theUE 102 and the eNB 104 implement the CSR determination from the block2402. For example, the block 2408 can include the reporting component116 of the UE 102 generating and transmitting CSRs according to a CSRconfiguration. By way of further example, the block 2408 can include theeNB 104 using the CSR in its downlink scheduling decisions.

In various embodiments, CSR reconfiguration can implicitly occur eachtime a process such as the process 2300 is executed. For example, theeNB 104 can instruct the UE 102 to send a CSR a certain number ofsubframes (e.g., one) prior to a start of a scheduled downlink packet.Stated somewhat differently, the CSR configurations can be definedrelative to the time-interval parameter. In these embodiments, upon eachreconfiguration of a time-interval parameter, the UE 102 can recognize,without specific instructions from the eNB 104, a corresponding CSRreconfiguration. Advantageously, such embodiments can result in reducedsignaling between the UE 102 and the eNB 104.

FIG. 25 illustrates an example of a timeline 2502 for reporting. In atypical embodiment, the timeline 2502 can result from a CSR optimizationprocess such as the process 2400 of FIG. 24. In the example of FIG. 25,a report periodicity is set to once per twenty subframes, and an offsetis such that a report is received by the eNB 104 one subframe prior todownlink transmission on a Physical Downlink Shared Channel (PDSCH).Based on each received report, the eNB 104 can decide to change a RBAand downlink MCS allocated to the UE 102 without releasing a downlinkSPS. Any changed MCS, for example, can be signaled to the UE 102 throughscheduling signaling on PDCCH. The new MCS can remain in effectindefinitely (e.g., until further notice, for a remainder of thedownlink SPS, etc.).

XVI. Examples of Implicit Downlink SPS Reconfiguration

In certain embodiments, downlink SPS can be designed to be implicitlyreconfigured when a eNB such as the eNB 104 triggers anSPS-reconfiguration event. In an example, the implicit-reconfigurationevent can be triggered by the eNB transmitting a certain number ofconsecutive empty packets (e.g., a MAC PDU with no MAC SDU). Particularcriteria for the SPS-reconfiguration event (e.g., the certain number ofempty packets) can be specified in an implicit-reconfiguration parameterof the downlink SPS. In various embodiments, theimplicit-reconfiguration event can be associated with a set of SPSreconfiguration settings (e.g., a configuration profile as describedabove). In general, the associated reconfiguration settings can besimilar to those described with respect to Tables 3-12. In that way, apreconfigured adjustment can occur and be communicated when the eNBtriggers the SPS-reconfiguration event.

In an example, a silence-interval configuration profile can beassociated with a SPS-reconfiguration event. If the SPS-reconfigurationevent is triggered by transmitting a certain number of empty packets asdescribed above, upon a detected transition from a talk spurt to asilence interval in downlink transmissions, the eNB 104 canunambiguously indicate to the UE 102 both the transition and acorresponding SPS reconfiguration by transmitting the certain number ofconsecutive empty packets (i.e., in downlink transmissionopportunities). According to this example, the UE 102 can detect thetransmission of the certain number of empty packets as a trigger of theSPS-reconfiguration event and immediately implement the silence-intervalconfiguration profile. An additional example will be described belowwith respect to FIG. 26.

FIG. 26 illustrates an example of a process 2600 for performing implicitdownlink SPS reconfiguration. The process 2600 can be implemented by anysystem that can process data and send/receive signals. For example, theprocess 2600, in whole or in part, can be implemented by one or more ofthe UE 102, the eNB 104, the UE 300, the UE 402, the eNB 406, theUE-side scheduler component 110, the UE-side reconfiguration component114, the UE-side reconfiguration settings component 120, the eNB-sidereconfiguration component 118, and/or the eNB-side reconfigurationsettings component 126. The process 2600 can also be performed generallyby the wireless communication system 100. Although any number ofsystems, in whole or in part, can implement the process 2600, tosimplify discussion, the process 2600 will be described in relation tothe UE 102 and/or the eNB 104, as appropriate.

At block 2602, downlink SPS is activated. In certain embodiments, thedownlink SPS can be activated via, for example, two signaling steps.First, the eNB 104 can send an SPS configuration to the UE 102 via RRCsignaling (e.g., at the RRC sublayer 516). Second, the eNB 104 can sendscheduling signaling (e.g., downlink control information (DCI) format 0)on a control channel (e.g., PDCCH, ePDCCH, etc.). The schedulinginformation can include, for example, a RBA and an MCS. In someembodiments, to indicate that this is not a regular DCI format 0 butrather one for SPS, the signaling can be addressed to an SPS Cell RadioNetwork Temporary Identifier (C-RNTI) of the UE 102 using, for example,specific bit patterns. A first SPS downlink transmission can bespecified to begin at subframe n. The downlink SPS can include, forexample, the parameters listed in Table 15 below.

TABLE 15 Parameter Description Time-Interval Parameter Interval betweenthe periodic (“semiPersistSchedIntervalUL”) transmission opportunities,in units of TTIs. m is set to this parameter valueImplicit-Reconfiguration Parameter If there has been no downlink data(“implicitReconfigurationAfter”) (e.g., only empty packets) afterimplicitReconfigurationAfter transmission opportunities, the SPS isreconfigured in a preconfigured manner.

In particular, Table 15 illustrates inclusion of animplicit-reconfiguration parameter in the downlink SPS. In general, theimplicit-reconfiguration parameter can define a trigger for anSPS-reconfiguration event. For example, the implicit-reconfigurationparameter can specify a certain number of consecutive empty packets asdescribed above. In a typical embodiment, the implicit-reconfigurationparameter is associated with a set of reconfiguration settings (e.g., aconfiguration profile for a silence interval). In certain embodiments,the set of reconfiguration settings can be determined and exchanged inany manner described above with respect to FIGS. 16-20.

At block 2604, the eNB 104 determines to reconfigure a configurationparameter of the downlink SPS. For example, the eNB 104 may identify atransition from a talk spurt to a silence interval. In variousembodiments, the block 2604 can include reconfiguring the downlink SPSaccordingly. At block 2606, the eNB 104 transmits the certain number ofempty packets (e.g., one or more) to trigger the SPS-reconfigurationevent. At block 2608, the UE 102 detects the trigger. As describedabove, the SPS-reconfiguration event is associated with a preconfiguredadjustment contained within reconfiguration settings. At block 2610, theUE 102 and the eNB 104 implement the reconfigured downlink SPS. Forexample, the eNB 104 may transmit downlink packets to the UE 102according to the reconfigured downlink SPS.

XVII. Examples of Downlink SPS Reconfiguration Combinations

It should be appreciated that various embodiments of downlink SPSreconfiguration can be combined in numerous fashions as described aboverelative to uplink SPS reconfiguration. In an example, at a transitioninstance in which the eNB 104 would like to reconfigure based on one oftwo alternative sets of reconfiguration settings (e.g., configurationprofiles), toggling can be used in a manner similar to that which isdescribed with respect to FIG. 13 relative to uplink SPSreconfiguration. As an alternative, in some embodiments, index signalingusing a reserved bit R can be used in a manner similar to that which isdescribed with respect to FIG. 14 relative to uplink SPSreconfiguration. As another alternative, in some embodiments, implicitdownlink SPS reconfiguration can be initiated as described with respectto FIG. 26 (e.g., for a transition from a talk spurt to a silenceinterval). According to this example, if the eNB 104 would like toreconfigure the downlink SPS differently than specified, for example, inthe two alternative sets of reconfiguration settings, explicit signalingto indicate a different set of reconfiguration settings can be used.Alternatively, the eNB 104 can explicitly indicate actual values, forexample, for a time-interval parameter, a packet-size profile, and/or astarting subframe, in scheduling signaling as described above.

In certain embodiments, additional signaling efficiency can be attainedwhen a same codec and/or a same ROHC implementation is used by the eNB104 for both uplink and downlink. If both uplink and downlink are basedon the same codec and ROHC implementation, SPS reconfiguration settingsfor uplink and downlink can also be the same. For example, assume thatthe eNB 104 determines downlink SPS reconfiguration settings andtransmits the downlink SPS reconfiguration settings to the UE 102. Ifthe UE 102 determines uplink SPS reconfiguration settings that are thesame as the downlink SPS reconfiguration settings, in some embodiments,the UE 102 can send only a signaling flag to the eNB 104. In theseembodiments, the UE 102 can avoid sending, for example, entire arrays.

Any suitable combination of various embodiments, or the featuresthereof, is contemplated. For example, any of the devices disclosedherein can include features of other embodiments. Thus, the eNB 104 mayhave any of the features described herein with respect to the eNB 406and the UE 102 may have any of the features described herein withrespect to the UE 300 and/or the UE 402. As another example, any stepsor blocks disclosed in a process herein may be used in other processesdescribed herein. Thus, a block of one of the processes described inFIGS. 7-26 may be used in any of the processes described in theseFigures.

In a typical embodiment, the method comprises establishing uplink SPSreconfiguration settings and wherein the uplink SPS reconfigurationsettings comprise an array of values for at least one of the followingthe time-interval parameter and a starting subframe. The establishingcomprises receiving proposed uplink SPS reconfiguration settings fromthe user device, transmitting acceptance of the proposed uplink SPSreconfiguration settings to the user device, and storing the proposeduplink SPS reconfiguration settings in memory, the proposed uplink SPSreconfiguration settings comprising the array of values. Prior to thetransmitting of the acceptance, verifying that the proposed uplink SPSreconfiguration settings satisfy at least one quality-of-servicecriterion.

The establishing comprises observing uplink packets from the userdevice, inferring the uplink SPS reconfiguration settings based, atleast in part, on the observing, transmitting the uplink SPSreconfiguration settings to the user device, and storing the uplink SPSreconfiguration settings in memory. The establishing further comprisesaccessing preconfigured stored settings based, at least in part, on acodec utilized by the user device and transmitting the preconfiguredstored settings to the user device.

In a typical embodiment, the uplink SPS reconfiguration settingscomprise an array of configuration profiles, each configuration profilein the array comprising a time-interval-parameter value and astarting-subframe identifier. In a typical embodiment the wirelessnetwork comprises a Long Term Evolution (LTE) network and the basestation and the user device exchange voice data over the LTE network.

In a typical embodiment, the method further comprises receiving from theuser device a subsequent request to reconfigure the already-activeuplink SPS, the subsequent request comprising subsequent informationrelated to a subsequent proposed adjustment, reconfiguring thealready-active uplink SPS, the reconfiguring comprising newly modifyingthe time-interval parameter based, at least in part, on the subsequentinformation, and sending new updated scheduling information to the userdevice, the new updated scheduling information comprising the newlymodified time-interval parameter.

In a typical embodiment, a method comprises, by a user device in awireless network, identifying a proposed adjustment to a time-intervalparameter of already-active uplink semi-persistent scheduling (SPS),wherein the already-active uplink SPS grants the user device a resourceblock allocation (RBA) and a modulation and coding scheme (MCS) forperiodic uplink transmissions, wherein the already-active uplink SPScomprises a time-interval parameter, the time-interval parameterspecifying a time interval between the periodic uplink transmissions,and transmitting to a base station a request to reconfigure thealready-active uplink SPS, the request comprising information related tothe proposed adjustment.

The method further comprises receiving notification of a reconfigurationof the already-active uplink SPS, the reconfiguration comprising amodified time-interval parameter and a starting subframe and sending anuplink transmission pursuant to the reconfiguration, wherein themodified time-interval parameter reflects the proposed adjustment, andwherein the modified time-interval parameter reflects an adjustment thatis different from the proposed adjustment.

In a typical embodiment, the method comprises transmitting to the basestation a subsequent request to reconfigure the already-active uplinkSPS, the subsequent request comprising subsequent information related toa subsequent proposed adjustment and receiving notification of asubsequent reconfiguration of the already-active uplink SPS, thesubsequent reconfiguration comprising a newly modified time-intervalparameter and a new starting subframe.

In a typical embodiment, the method comprises, prior to the transmittingof the request to reconfigure, sending an uplink-grant request to thebase station, receiving an allocation of an uplink grant responsive tothe uplink-grant request, wherein the request to reconfigure istransmitted pursuant to the uplink grant, wherein the uplink-grantrequest is a scheduling request, wherein the uplink-grant request isspecified using one or more reserved bits of a header of an uplinkpacket, wherein the request to reconfigure is specified in at least oneof the following portions of a media access control (MAC) protocol dataunit (PDU) a reserved bit of a header of the MAC PDU, a control-elementfield of a payload of the MAC PDU, and a padding field of the payload.

In a typical embodiment, the request to reconfigure is specified in acontrol-element field of a media access control (MAC) payload, thecontrol-element field identified by a logical channel ID (LCID) valueassigned from a set of reserved LCID values and the information relatedto the proposed adjustment comprises a proposed value of thetime-interval parameter, wherein the information related to the proposedadjustment comprises an index to an array of time-interval-parametervalues stored in memory on the user device.

In a typical embodiment, the time-interval parameter comprises twopossible values, the two possible values comprising a current value andan alternative value and the request comprises a toggle indicator, thetoggle indicator comprising the information related to the proposedadjustment, the toggle indicator requesting that the time-intervalparameter be toggled to the alternative value, wherein one of the twopossible values corresponds to a talk spurt and another of the twovalues corresponds to a silence interval, and wherein the informationrelated to the proposed adjustment identifies a proposed startingsubframe.

In a typical embodiment, prior to the transmitting of the request forreconfiguration, sending an uplink transmission pursuant to thealready-active uplink SPS, wherein the identifying comprises determininga transition on the user device, wherein the determined transition isselected from the group consisting of a transition from a talk spurt toa silence interval, and a transition from a silence interval to a talkspurt.

In a typical embodiment, establishing uplink SPS reconfigurationsettings and the uplink SPS reconfiguration settings comprise an arrayof values for at least one of the following the time-interval parameterand a starting subframe.

In a typical embodiment, the establishing comprises determining theuplink SPS reconfiguration settings, transmitting the uplink SPSreconfiguration settings to the base station, receiving an acceptance ofthe uplink SPS reconfiguration settings, and storing the uplink SPSreconfiguration settings in memory. The determining comprises observingintervals and transition spacing at an output of a vocoder resident onthe user device, inferring the uplink SPS reconfiguration settingsbased, at least in part, on the observing, and receiving the uplink SPSreconfiguration settings from a vocoder resident on the user device. Theestablishing comprises receiving the uplink SPS reconfiguration settingsfrom the base station and storing the uplink SPS reconfigurationsettings in memory. The uplink SPS reconfiguration settings comprise anarray of configuration profiles, each configuration profile in the arraycomprising a time-interval-parameter value and a starting-subframeidentifier. The wireless network comprises a Long Term Evolution (LTE)network and the base station and the user device exchange voice dataover the LTE network.

In a typical embodiment a method comprises, by a base station in awireless network, receiving from a user device a request to reconfigurealready-active uplink semi-persistent scheduling (SPS) to accommodate atleast one packet-size change, wherein the already-active uplink SPScomprises a modulation and coding scheme (MCS) and a resource blockallocation (RBA) for periodic uplink transmissions, wherein the requestcomprises information related to a size of each of one or more futureuplink packets, and reconfiguring the already-active uplink SPS, thereconfiguring comprising modifying at least one of the RBA and the MCSto accommodate at least a next packet of the one or more future uplinkpackets. Prior to the reconfiguring, determining whether to reconfigurethe already-active uplink SPS responsive to the request, notifying theuser device of the modified at least one of the RBA and the MCS, andreceiving from the user device an uplink transmission pursuant to thereconfigured already-active uplink SPS.

In a typical embodiment, the one or more future uplink packets comprisea plurality of packets of non-uniform size, reconfiguring thealready-active uplink SPS without further request from the user device,the reconfiguring comprising newly modifying at least one of the RBA andthe MCS to accommodate a subsequent packet of the one or more futureuplink packets, and notifying the user device of the newly modified atleast one of the RBA and the MCS. The information comprises the size ofeach of the one or more future uplink packets. The information comprisesan index to a particular packet-size profile in an array of packet-sizeprofiles stored in memory on the base station, wherein the modifyingcomprises accommodating at least a next packet of the particularpacket-size profile, wherein the request specifies the index in areserved bit of a media access control (MAC) header. The particularpacket-size profile comprise a range of packet sizes and the modifyingcomprising accommodating the range of packet sizes.

In a typical embodiment, the method further comprises receiving apacket-size-override request relative to the particular packet-sizeprofile, the packet-size-override request comprising an override sizeand a specified number of packets, reconfiguring the already-activeuplink SPS, the reconfiguring comprising modifying at least one of theRBA and the MCS to accommodate the override size for the specifiednumber of packets, and reconfiguring the already-active uplink SPS afterthe specified number of packets, the reconfiguring comprising modifyingat least one of the RBA and the MCS to accommodate at least a nextpacket of the particular packet-size profile. The information comprisesan index to a particular packet-size profile in an array of packet-sizeprofiles stored in memory on the base station, a packet-size-overriderequest relative to the particular packet-size profile, thepacket-size-override request comprising an override size and a specifiednumber of packets, and wherein the modifying comprises accommodating theoverride size for the specified number of packets.

In a typical embodiment, the already-active uplink SPS comprises atime-interval parameter, the time-interval parameter specifying a timeinterval between the periodic uplink transmissions, wherein the requestcomprises information related to a proposed adjustment of thetime-interval parameter, and wherein the reconfiguring comprisesmodifying the time-interval parameter based, at least in part, on theinformation related to the proposed adjustment. The request specifies anindex to a particular configuration profile in an array of configurationprofiles stored in memory on the base station, the index is theinformation related to the proposed adjustment of the time-intervalparameter and the information related to the size of each of the one ormore future uplink packets, the particular configuration profilecomprises a packet-size profile and a time-interval-parameter value, themodifying of the at least one of the RBA and the MCS comprisesaccommodating at least a next packet of the packet-size profile, and themodifying of the time-interval parameter comprises setting thetime-interval parameter to the time-interval-parameter value. Thealready-active uplink SPS toggles between two packet-size profiles, thetwo packet-size profiles comprising a current packet-size profile and analternative packet-size profile, wherein the information comprises atoggle indicator, and the modifying comprises accommodating at least anext packet of the alternative packet-size profile. One of the twopacket-size profiles corresponds to a talk spurt and another of the twopacket-size profiles corresponds to a silence interval.

In a typical embodiment, the method further comprises receiving apacket-size-override request relative to a packet-size profile, thepacket-size-override request comprising an override size and a number ofpackets. The request to reconfigure is responsive to at least one of thefollowing a determined change in Robust Header Compression (ROHC) state,a determined change in ROHC mode, a determined transition from a talkspurt to a silence interval, and a determined transition from a silenceinterval to a talk spurt. The request to reconfigure is responsive to acodec-related packet fluctuation.

In a typical embodiment, prior to the receiving of the request forreconfiguration, receiving an uplink transmission pursuant to thealready-active uplink SPS and prior to the reconfiguring, verifying thatthe request for reconfiguration satisfies at least onequality-of-service criterion. The method further comprises establishinguplink SPS reconfiguration settings and wherein the uplink SPSreconfiguration settings comprise an array of packet-size profiles.

The establishing comprises receiving proposed uplink SPS reconfigurationsettings from the user device, verifying that the proposed uplink SPSreconfiguration settings satisfy at least one quality-of-servicecriterion, responsive to successful verification, transmittingacceptance of the proposed uplink SPS reconfiguration settings to theuser device, storing the proposed uplink SPS reconfiguration settings,the proposed uplink SPS reconfiguration settings comprising the array ofpacket-size profiles, observing uplink packets from the user device,inferring the uplink SPS reconfiguration settings based, at least inpart, on the observing, transmitting the uplink SPS reconfigurationsettings to the user device, storing the uplink SPS reconfigurationsettings in memory, accessing preconfigured stored settings based, atleast in part, on a codec utilized by the user device, and transmittingthe preconfigured stored settings to the user device.

In a typical embodiment, the uplink SPS reconfiguration settingscomprise an array of configuration profiles, each configuration profilein the array comprising a time-interval-parameter value, a packet-sizeprofile, starting-subframe identifier. The wireless network comprises aLong Term Evolution (LTE) network and the base station and the userdevice exchange voice data over the LTE network.

In a typical embodiment, a method comprising, by a user device in awireless network, determining at least one packet-size change in one ormore future uplink packets, transmitting to a base station a request toreconfigure already-active uplink SPS to accommodate the at least onepacket-size change, wherein the already-active uplink SPS comprises amodulation and coding scheme (MCS) and a resource block allocation (RBA)for periodic uplink transmissions, and wherein the request comprisesinformation related to a size of each of one or more future uplinkpackets. The method further comprises receiving notification of areconfiguration of the already-active uplink SPS, the reconfigurationcomprising at least one of a modified RBA and a modified MCS, sending anuplink transmission pursuant to the reconfiguration, wherein the one ormore future uplink packets comprise a plurality of packets ofnon-uniform size, and receiving notification of a subsequentreconfiguration of the already-active uplink SPS without further requestfrom the user device, the subsequent reconfiguration comprising at leastone of a newly modified RBA and a newly modified MCS to accommodate asubsequent packet of the one or more future uplink packets. In a typicalembodiment, the information comprises the size of each of the one ormore future uplink packets.

In a typical embodiment, the information comprises an index to aparticular packet-size profile in an array of packet-size profilesstored in memory on the user device and receiving notification of areconfiguration of the already-active uplink SPS, the reconfigurationcomprising at least one of a modified RBA and a modified MCS that arebased, at least in part, on the particular packet-size profile. Therequest specifies the index in a reserved bit of a media access control(MAC) header. The particular packet-size profile comprise a range ofpacket sizes and the at least one of a modified RBA and a modified MCSis based, at least in part, on the range of packet sizes.

In a typical embodiment, the method further comprises transmitting apacket-size-override request relative to the particular packet-sizeprofile, the packet-size-override request comprising an override sizeand a specified number of packets, receiving notification of areconfiguration of the already-active uplink SPS, the reconfigurationcomprising at least one of a modified RBA and a modified MCS that isbased, at least in part, on the packet-size-override request, and afterthe specified number of packets, receiving notification of areconfiguration of the already-active uplink SPS, the reconfigurationcomprising at least one of a newly modified RBA and a newly modifiedMCS.

The information comprises an index to a particular packet-size profilein an array of packet-size profiles stored in memory on the basestation, a packet-size-override request relative to the particularpacket-size profile, the packet-size-override request comprising anoverride size and a specified number of packets, and receivingnotification of a reconfiguration of the already-active uplink SPS, thereconfiguration comprising at least one of a modified RBA and a modifiedMCS that is based, at least in part, on the packet-size-overriderequest. The already-active uplink SPS comprises a time-intervalparameter, the time-interval parameter specifying a time intervalbetween the periodic uplink transmissions, wherein the request comprisesinformation related to a proposed adjustment of the time-intervalparameter, and receiving notification of a reconfiguration of thealready-active uplink SPS, the reconfiguration comprising a modifiedtime-interval parameter and at least one of a modified RBA and amodified MCS.

In a typical embodiment, the request specifies an index to a particularconfiguration profile in an array of configuration profiles stored inmemory on the user device, the index is the information related to theproposed adjustment of the time-interval parameter and the informationrelated to the size of each of the one or more future uplink packets,and the particular configuration profile comprises a packet-size profileand a time-interval-parameter value. The already-active uplink SPStoggles between two packet-size profiles, the two packet-size profilescomprising a current packet-size profile and an alternative packet-sizeprofile, wherein the information comprises a toggle indicator, andreceiving notification of a reconfiguration to the already-active uplinkSPS, the reconfiguration comprising at least one of a modified RBA and amodified MCS that is based, at least in part, on the alternativepacket-size profile. One of the two packet-size profiles corresponds toa talk spurt and another of the two packet-size profiles corresponds toa silence interval.

In a typical embodiment, the method further comprises transmitting tothe base station a packet-size-override request relative to apacket-size profile, the packet-size-override request comprising anoverride size and a number of packets. The determining comprisesdetermining a transition on the user device and the determinedtransition is selected from the group consisting of a determined changein Robust Header Compression (ROHC) state and a determined change inROHC mode.

In a typical embodiment, the determined transition is selected from thegroup consisting of a determined transition from a talk spurt to asilence interval and a determined transition from a silence interval toa talk spurt. The determined transition comprises a codec-related packetfluctuation. Prior to the transmitting of the request forreconfiguration, sending an uplink transmission pursuant to thealready-active uplink SPS and wherein the one or more future uplinkpackets relate to voice data.

In a typical embodiment, the method further comprises establishinguplink SPS reconfiguration settings and wherein the uplink SPSreconfiguration settings comprise an array of packet-size profiles. Theestablishing comprises determining the uplink SPS reconfigurationsettings, transmitting the uplink SPS reconfiguration settings to thebase station, receiving an acceptance of the uplink SPS reconfigurationsettings, and storing the uplink SPS reconfiguration settings in memory.The determining comprises observing packet sizes at an output of avocoder resident on the user device, inferring the uplink SPSreconfiguration settings based, at least in part, on the observing, andreceiving the uplink SPS reconfiguration settings from a vocoderresident on the user device. The establishing comprises receiving theuplink SPS reconfiguration settings from the base station and storingthe uplink SPS reconfiguration settings in memory. The uplink SPSreconfiguration settings comprise an array of configuration profiles,each configuration profile in the array comprising a packet-sizeprofile, a time-interval-parameter value, and a starting-subframeidentifier. In a typical embodiment, the wireless network comprises aLong Term Evolution (LTE) network and the base station and the userdevice exchange voice data over the LTE network.

In a typical embodiment, a method comprising, by a base station in awireless network, detecting a trigger, by a user device subject toalready-active uplink semi-persistent scheduling (SPS), of aSPS-reconfiguration event, wherein the already-active uplink SPS grantsthe user device a resource block allocation (RBA) and a modulation andcoding scheme (MCS) for periodic uplink transmissions, wherein thealready-active uplink SPS comprises a time-interval parameter, thetime-interval parameter specifying a time interval between the periodicuplink transmissions, wherein the detected trigger comprisestransmission by the user device of one or more empty packets, whereinthe SPS-reconfiguration event is associated with a preconfiguredadjustment to at least one configuration parameter of the already-activeuplink SPS, and reconfiguring the already-active uplink SPS based, atleast in part, on the preconfigured adjustment. The already-activeuplink SPS comprises an implicit-reconfiguration parameter thatspecifies a number of the one or more empty packets. Each empty packetcomprises a media access control (MAC) protocol data unit (PDU) with noMAC service data unit (SDU).

In a typical embodiment, the method comprising, prior to the detecting,establishing uplink SPS reconfiguration settings and wherein the uplinkSPS reconfiguration settings specify the preconfigured adjustment. Theestablishing comprises receiving proposed uplink SPS reconfigurationsettings from the user device, transmitting acceptance of the proposeduplink SPS reconfiguration settings to the user device, and storing theproposed uplink SPS reconfiguration settings in memory. Prior to thetransmitting of the acceptance, verifying that the proposed uplink SPSreconfiguration settings satisfy at least one quality-of-servicecriterion.

The establishing comprises observing uplink packets from the userdevice, inferring the uplink SPS reconfiguration settings based, atleast in part, on the observing, transmitting the uplink SPSreconfiguration settings to the user device, and storing the uplink SPSreconfiguration settings in memory.

The establishing comprises accessing preconfigured stored settingsbased, at least in part, on a codec utilized by the user device andtransmitting the preconfigured stored settings to the user device. Theuplink SPS reconfiguration settings comprise an array of configurationprofiles, each configuration profile in the array comprising one or moreof a packet-size profile, a time-interval-parameter value, and astarting-subframe identifier, wherein the SPS reconfiguration event isresponsive to a determined transition on the user device, wherein thedetermined transition comprises a transition from a talk spurt to asilence interval, wherein the preconfigured adjustment relates to apacket size accommodated by the reconfigured already-active uplink SPS,and wherein the preconfigured adjustment comprises a modification to thetime-interval parameter. The method further comprising, prior to thereconfiguring, verifying that the preconfigured adjustment satisfies atleast one quality-of-service criterion.

In a typical embodiment, a method comprising, by a user device in awireless network, identifying at least one configuration parameter ofalready-active uplink semi-persistent scheduling (SPS) for adjustment,wherein the already-active uplink SPS grants the user device a resourceblock allocation (RBA) and a modulation and coding scheme (MCS) forperiodic uplink transmissions, wherein the already-active uplink SPScomprises a time-interval parameter, the time-interval parameterspecifying a time interval between the periodic uplink transmissions,responsive to the identifying, triggering a SPS-reconfiguration event,the triggering comprising transmitting to a base station one or moreempty packets, and wherein the SPS-reconfiguration event is associatedwith a preconfigured adjustment to the at least one configurationparameter.

The already-active uplink SPS comprises an implicit-reconfigurationparameter that specifies a number of the one or more empty packets. Eachempty packet comprises a media access control (MAC) protocol data unit(PDU) with no MAC service data unit (SDU).

In a typical embodiment, the method further comprising, prior to theidentifying establishing uplink SPS reconfiguration settings and whereinthe uplink SPS reconfiguration settings specify the preconfiguredadjustment. The establishing comprises determining the uplink SPSreconfiguration settings, transmitting the uplink SPS reconfigurationsettings to the base station, receiving an acceptance of the uplink SPSreconfiguration settings, and storing the uplink SPS reconfigurationsettings in memory. The determining comprises observing packet sizes atan output of a vocoder resident on the user device and inferring theuplink SPS reconfiguration settings based, at least in part, on theobserving. The determining comprises receiving the uplink SPSreconfiguration settings from a vocoder resident on the user device. Theestablishing comprises receiving the uplink SPS reconfiguration settingsfrom the base station and storing the uplink SPS reconfigurationsettings in memory.

In a typical embodiment, the uplink SPS reconfiguration settingscomprise an array of configuration profiles, each configuration profilein the array comprising one or more of a packet-size profile, atime-interval-parameter value, and a starting-subframe identifier. Thewireless network comprises a Long Term Evolution (LTE) network and thebase station and the user device exchange voice data over the LTEnetwork. The identifying comprises determining a transition on the userdevice, wherein the determined transition comprises a transition from atalk spurt to a silence interval, wherein the preconfigured adjustmentwherein the preconfigured adjustment relates to a packet sizeaccommodated by the already-active uplink SPS, and wherein thepreconfigured adjustment comprises a modification to the time-intervalparameter.

In a typical embodiment, a method comprising, by a base station in awireless network, responsive to a reconfiguration determination,reconfiguring already-active downlink semi-persistent scheduling (SPS)to accommodate a plurality of non-uniformly-sized future downlinkpackets, wherein the already-active downlink SPS grants a user device aresource block allocation (RBA) and a modulation and coding scheme (MCS)for periodic downlink transmissions, wherein the already-active downlinkSPS comprises a time-interval parameter, the time-interval parameterspecifying a time interval between the periodic downlink transmissions,and sending to the user device a notification of the reconfiguredalready-active downlink SPS, the notification comprising informationrelated to a size of each of the plurality of non-uniformly-sized futuredownlink packets.

In a typical embodiment, the method further comprises transmitting tothe user device a downlink transmission pursuant to the reconfiguredalready-active downlink SPS, wherein the information comprises the sizeof each of the plurality of non-uniformly-sized future downlink packets,wherein the information comprises an index to a particular packet-sizeprofile in an array of packet-size profiles stored in memory on the basestation, wherein the reconfiguring comprises modifying at least one ofthe RBA and the MCS to accommodate at least a next packet of theparticular packet-size profile, and wherein the notification specifiesthe index in a reserved bit of a media access control (MAC) header. Theparticular packet-size profile comprise a range of packet sizes and themodifying comprising modifying the at least one of the RBA and the MCSto accommodate the range of packet sizes.

In a typical embodiment, the method further comprises reconfiguring thealready-active downlink SPS to accommodate a packet-size overriderelative to the particular packet-size profile, wherein the packet-sizeoverride comprises an override size for a specified number of packets,wherein the reconfiguring comprises modifying at least one of the RBAand the MCS to accommodate the override size, and notifying the userdevice of the packet-size override. Reconfiguring the already-activedownlink SPS after the specified number of packets, the reconfiguringcomprising modifying at least one of the RBA and the MCS to accommodateat least a next packet of the particular packet-size profile, whereinthe notification comprises information related to a proposed adjustmentof the time-interval parameter and the reconfiguring of thealready-active downlink SPS comprises modifying at least one of the RBAand the MCS to accommodate at least a next packet of the plurality ofnon-uniformly-sized future downlink packets and modifying thetime-interval parameter based, at least in part, on the informationrelated to the proposed adjustment.

The notification specifies an index to a particular configurationprofile in an array of configuration profiles stored in memory on thebase station, the index is the information related to the proposedadjustment of the time-interval parameter and the information related tothe size of each of the plurality of non-uniformly-sized future downlinkpackets, the particular configuration profile comprises a packet-sizeprofile and a time-interval-parameter value, the modifying of the atleast one of the RBA and the MCS comprises accommodating at least a nextpacket of the packet-size profile, and the modifying of thetime-interval parameter comprises setting the time-interval parameter tothe time-interval-parameter value. The already-active downlink SPStoggles between two packet-size profiles, the two packet-size profilescomprising a current packet-size profile and an alternative packet-sizeprofile, wherein the information comprises a toggle indicator, and thereconfiguring comprises modifying at least one of the RBA and the MCS toaccommodate at least a next packet of the alternative packet-sizeprofile. One of the two packet-size profiles corresponds to a talk spurtand another of the two packet-size profiles corresponds to a silenceinterval.

In a typical embodiment, the reconfiguration determination is responsiveto at least one of the following a determined change in Robust HeaderCompression (ROHC) state, a determined change in ROHC mode, a determinedtransition from a talk spurt to a silence interval, a determinedtransition from a silence interval to a talk spurt, and wherein thereconfiguration determination is responsive to a codec-related packetfluctuation. Prior to the reconfiguration determination, transmitting adownlink transmission pursuant to the already-active downlink SPS. Themethod further comprises establishing downlink SPS reconfigurationsettings and wherein the downlink SPS reconfiguration settings comprisean array of packet-size profiles.

The establishing comprises receiving proposed downlink SPSreconfiguration settings from the user device, verifying that theproposed downlink SPS reconfiguration settings satisfy at least onequality-of-service criterion, responsive to successful verification,transmitting acceptance of the proposed downlink SPS reconfigurationsettings to the user device, and storing the proposed downlink SPSreconfiguration settings, the proposed downlink SPS reconfigurationsettings comprising the array of packet-size profiles.

The establishing comprises observing downlink packets, inferring thedownlink SPS reconfiguration settings based, at least in part, on theobserving, transmitting the downlink SPS reconfiguration settings to theuser device, storing the downlink SPS reconfiguration settings inmemory, accessing preconfigured stored settings, and transmitting thepreconfigured stored settings to the user device. The downlink SPSreconfiguration settings comprise an array of configuration profiles,each configuration profile in the array comprising atime-interval-parameter value, a packet-size profile, starting-subframeidentifier, wherein the wireless network comprises a Long Term Evolution(LTE) network and the base station and the user device exchange voicedata over the LTE network.

In a typical embodiment, a method comprising, by a user device in awireless network, receiving from a base station a notification ofreconfigured downlink semi-persistent scheduling (SPS), wherein thereconfigured downlink SPS reconfigures already-active downlink SPS toaccommodate a plurality of non-uniformly-sized future downlink packets,wherein the already-active downlink SPS grants the user device aresource block allocation (RBA) and a modulation and coding scheme (MCS)for periodic downlink transmissions, wherein the already-active downlinkSPS comprises a time-interval parameter, the time-interval parameterspecifying a time interval between the periodic downlink transmissions,wherein the notification comprises information related to a size of eachof the plurality of non-uniformly-sized future downlink packets, andimplementing the reconfigured downlink SPS. The implementing comprisingreceiving a downlink transmission pursuant to the reconfigured downlinkSPS.

In a typical embodiment, the method further comprises receivingnotification of a subsequent reconfiguration of the already-activedownlink SPS, the subsequent reconfiguration comprising at least one ofa newly modified RBA and a newly modified MCS to accommodate asubsequent packet of the plurality of non-uniformly-sized futuredownlink packets, wherein the information comprises the size of each ofthe plurality of non-uniformly-sized future downlink packets, whereinthe information comprises an index to a particular packet-size profilein an array of packet-size profiles stored in memory on the user device,wherein the reconfiguration comprises at least one of a modified RBA anda modified MCS that is based, at least in part, on the particularpacket-size profile, wherein the notification specifies the index in areserved bit of a media access control (MAC) header, wherein theparticular packet-size profile comprise a range of packet sizes andwherein the modified at least one of the RBA and the MCS accommodatesthe range of packet sizes.

In a typical embodiment, the notification comprises information relatedto a modified time-interval parameter, the notification specifies anindex to a particular configuration profile in an array of configurationprofiles stored in memory on the user device, the index is theinformation related to the modified time-interval parameter and theinformation related to the size of each of the plurality ofnon-uniformly-sized future downlink packets, and the particularconfiguration profile comprises a packet-size profile and atime-interval-parameter value.

In a typical embodiment, the method further comprises, prior to thereceiving of the notification, receiving a downlink transmissionpursuant to the already-active downlink SPS. Receiving downlink SPSreconfiguration settings from the base station and storing the downlinkSPS reconfiguration settings in memory. The downlink SPS reconfigurationsettings comprise an array of configuration profiles, each configurationprofile in the array comprising a packet-size profile, atime-interval-parameter value, and a starting-subframe identifier andwherein the wireless network comprises a Long Term Evolution (LTE)network and the base station and the user device exchange voice dataover the LTE network.

In a typical embodiment, a method comprising, by a base station in awireless network, responsive to a reconfiguration determination,reconfiguring already-active downlink semi-persistent scheduling (SPS),the reconfiguring comprising modifying a time-interval parameter of thealready-active downlink SPS, wherein the already-active downlink SPSgrants a user device a resource block allocation and a modulation andcoding scheme (MCS) for periodic downlink transmissions, wherein thetime-interval parameter specifies a time interval between the periodicdownlink transmissions, sending to the user device a notification of thereconfigured already-active downlink SPS, determining one or more timeswhen the user device should send a channel status report (CSR) to thebase station based, at least in part, on the modified time-intervalparameter, and transmitting to the user device information sufficient toidentify the determined one or more times.

In a typical embodiment, the determining comprises determining a CSRconfiguration based, at least in part, on the modified time-intervalparameter, the CSR configuration specifies, in terms of the modifiedtime-interval parameter, when the user device should send a CSR to thebase station, the CSR configuration comprising a periodic interval andan offset, and the transmitting comprises transmitting to the userdevice information sufficient to identify the CSR configuration. Themethod further comprises receiving a CSR pursuant to the determined oneor more times and making a scheduling decision based, at least in part,on the received CSR.

In a typical embodiment, a method comprising, by a user device in awireless network, receiving, from a base station, a notification ofreconfigured downlink SPS, wherein the reconfigured downlink SPSreconfigures already-active downlink SPS, wherein the already-activedownlink SPS grants the user device a resource block allocation (RBA)and a modulation and coding scheme (MCS) for periodic downlinktransmissions, wherein the already-active downlink SPS comprises atime-interval parameter, the time-interval parameter specifying a timeinterval between the periodic downlink transmissions, wherein thereconfigured downlink SPS comprises a modified time-interval parameter,and receiving from the base station information sufficient to identifyone or more times at which a channel status report (CSR) should be sent.The information comprises a CSR configuration and the CSR configurationspecifies, in terms of the modified time-interval parameter, when theuser device should send a CSR to the base station, the CSR configurationcomprising a periodic interval and an offset. The method furthercomprises transmitting a CSR to the base station pursuant to theinformation.

Herein, reference to a computer-readable storage medium encompasses oneor more tangible computer-readable storage media possessing structures.As an example and not by way of limitation, a computer-readable storagemedium may include a semiconductor-based or other integrated circuit(IC) (such, as for example, a field-programmable gate array (FPGA) or anapplication-specific IC (ASIC)), a hard disk, an HDD, a hybrid harddrive (HHD), an optical disc, an optical disc drive (ODD), amagneto-optical disc, a magneto-optical drive, a floppy disk, a floppydisk drive (FDD), magnetic tape, a holographic storage medium, asolid-state drive (SSD), a RAM-drive, a SECURE DIGITAL card, a SECUREDIGITAL drive, a flash memory card, a flash memory drive, or any othersuitable tangible computer-readable storage medium or a combination oftwo or more of these, where appropriate. In particular embodiments, oneor more computer-readable storage media embody encoded software.

Herein, reference to encoded software may encompass one or moreapplications, bytecode, one or more computer programs, one or moreexecutables, one or more instructions, logic, machine code, one or morescripts, or source code, and vice versa, where appropriate, that havebeen stored or encoded in a computer-readable storage medium. Inparticular embodiments, encoded software includes one or moreapplication programming interfaces (APIs) stored or encoded in acomputer-readable storage medium. Particular embodiments may use anysuitable encoded software written or otherwise expressed in any suitableprogramming language or combination of programming languages stored orencoded in any suitable type or number of computer-readable storagemedia. In particular embodiments, encoded software may be expressed assource code or object code. In particular embodiments, encoded softwareis expressed in a higher-level programming language, such as, forexample, C, Perl, or a suitable extension thereof. In particularembodiments, encoded software is expressed in a lower-level programminglanguage, such as assembly language (or machine code). In particularembodiments, encoded software is expressed in JAVA. In particularembodiments, encoded software is expressed in Hyper Text Markup Language(HTML), Extensible Markup Language (XML), or other suitable markuplanguage.

Depending on the embodiment, certain acts, events, or functions of anyof the algorithms described herein can be performed in a differentsequence, can be added, merged, or left out altogether (e.g., not alldescribed acts or events are necessary for the practice of thealgorithms). Moreover, in certain embodiments, acts or events can beperformed concurrently, e.g., through multi-threaded processing,interrupt processing, or multiple processors or processor cores or onother parallel architectures, rather than sequentially. Although certaincomputer-implemented tasks are described as being performed by aparticular entity, other embodiments are possible in which these tasksare performed by a different entity.

Conditional language used herein, such as, among others, “can,” “might,”“may,” “e.g.,” and the like, unless specifically stated otherwise, orotherwise understood within the context as used, is generally intendedto convey that certain embodiments include, while other embodiments donot include, certain features, elements and/or states. Thus, suchconditional language is not generally intended to imply that features,elements and/or states are in any way required for one or moreembodiments or that one or more embodiments necessarily include logicfor deciding, with or without author input or prompting, whether thesefeatures, elements and/or states are included or are to be performed inany particular embodiment.

While the above detailed description has shown, described, and pointedout novel features as applied to various embodiments, it will beunderstood that various omissions, substitutions, and changes in theform and details of the devices or algorithms illustrated can be madewithout departing from the spirit of the disclosure. As will berecognized, the processes described herein can be embodied within a formthat does not provide all of the features and benefits set forth herein,as some features can be used or practiced separately from others. Thescope of protection is defined by the appended claims rather than by theforegoing description. All changes which come within the meaning andrange of equivalency of the claims are to be embraced within theirscope.

Although various embodiments of the method and apparatus of the presentinvention have been illustrated in the accompanying Drawings anddescribed in the foregoing Detailed Description, it will be understoodthat the invention is not limited to the embodiments disclosed, but iscapable of numerous rearrangements, modifications and substitutionswithout departing from the spirit of the invention as set forth herein.

What is claimed is:
 1. A method comprising, by a base station in a wireless network: configuring uplink semi-persistent scheduling (SPS) for a user equipment; receiving from a user equipment a request to reconfigure the already-active uplink SPS, wherein the already-active uplink SPS grants the user equipment a resource block allocation (RBA) and a modulation and coding scheme (MCS) for periodic uplink transmissions, wherein the already-active uplink SPS comprises a time-interval parameter, the time-interval parameter specifying a time interval between the periodic uplink transmissions, wherein the request comprises information related to a proposed adjustment of the time-interval parameter; and sending a reconfigured already-active uplink SPS to the user equipment, the reconfigured already-active uplink SPS comprising a modified time-interval parameter based, at least in part, on the information.
 2. The method of claim 1, comprising notifying the user device of the reconfigured already-active uplink SPS.
 3. The method of claim 1, comprising receiving from the user device an uplink transmission pursuant to the reconfigured already-active uplink SPS.
 4. The method of claim 1, wherein the reconfigured already-active uplink SPS comprises a starting-subframe identifier.
 5. The method of claim 1, comprising sending updated scheduling information to the user equipment, the updated scheduling information comprising the modified time-interval parameter.
 6. The method of claim 1, comprising receiving an uplink-grant request from the user equipment prior to receiving the request to reconfigure.
 7. The method of claim 6, wherein the uplink-grant request is a scheduling request.
 8. The method of claim 6, wherein the uplink-grant request is specified using one or more reserved bits of a header of an uplink packet.
 9. The method of claim 1, wherein the request to reconfigure is specified in at least one of the following portions of a media access control (MAC) protocol data unit (PDU): a reserved bit of a header of the MAC PDU; a control-element field of a payload of the MAC PDU; and a padding field of the payload.
 10. The method of claim 1, wherein the request to reconfigure is specified in a control-element field of a media access control (MAC) payload, the control-element field identified by a logical channel ID (LCID) value assigned from a set of reserved LCID values.
 11. The method of claim 1, wherein the information related to the proposed adjustment comprises a proposed value of the time-interval parameter.
 12. The method of claim 1, wherein the information related to the proposed adjustment comprises an index to an array of time-interval-parameter values stored in memory on the base station.
 13. The method of claim 1, wherein the time-interval parameter comprises two possible values, the two possible values comprising a current value and an alternative value, and wherein the information related to the proposed adjustment comprises a toggle indicator.
 14. The method of claim 13, wherein one of the two possible values corresponds to a talk spurt and another of the two possible values corresponds to a silence interval.
 15. The method of claim 1, wherein the information related to the proposed adjustment identifies a proposed starting subframe. 